After 8 years developing server and embedded applications using Hibernate as an ORM, squeezing my brain seeking solutions to improve Hibernate performance while reading blogs and attending conferences, I decided to share some of the knowledge that was acquired during these tumultuous years.
In this article we see exactly what happens when Hibernate detects a dirty collection that it must re-create, and how this process effects the performance of your applications.
Not just parts, the whole framework is a leak. I have no doubt that the author can write "many more posts". Hibernate users are forced to know the frameworks innards in order to use it painlessly. Hibernate simply tried too much. It duplicated the database as Java framework. Now that it's cemented as JPA Standard programmers need to abstract from the abstractions and find a sane subset suitable for practical purposes.
I would always use a code-generator to uniformly create simple Entity classes and avoid all 'fancy' configuration options and Annotations, such as 'cascade'. Uniformity and simplicity are crucial for predictable Hibernate behavior.
I would always use a code-generator to uniformly create simple Entity classes and avoid all 'fancy' configuration options and Annotations, such as 'cascade'.
Can you tell us what code generator you use. Is this producing plain jdbc call's ?
Txs in advance
