I am going through the Hibernate documentation and came across the concept of Hibernate Dynamic Models : http://docs.jboss.org/hibernate/orm/3.6/reference/en-US/html/persistent-classes.html#persistent-classes-dynamicmodels
I understood that using Dynamic Models concept we need not write any POJO classes separately and we just need to write a mapping file. Practically when we will be using this feature?
Also the document says:
Quote:
One of the main advantages of dynamic mapping is quick turnaround time for prototyping, without the need for entity class implementation. However, you lose compile-time type checking and will likely deal with many exceptions at runtime. As a result of the Hibernate mapping, the database schema can easily be normalized and sound, allowing to add a proper domain model implementation on top later on.
Can you please help me in understanding the advantages of it, I was not able to get what it means.
Also the document says:
Code:
Session dynamicSession = pojoSession.getSession(EntityMode.MAP);
Quote:
Please note that the call to getSession() using an EntityMode is on the Session API, not the SessionFactory. That way, the new Session shares the underlying JDBC connection, transaction, and other context information. This means you do not have to call flush() and close() on the secondary Session, and also leave the transaction and connection handling to the primary unit of work.
In this I understand that pojoSession is same as Session object and what is the secondary Session as per the statements.
Please help me in understanding the dynamic models concept of Hibernate 3.x.
Login
FAQ
Search