Hibernate version: 3.2

Name and version of the database you are using: Oracle 10G


We never use lazy instantiation. I'm in the process of upgrading from 2.1.6 to 3.2. This has become a nightmare because of the change from the default lazy instantiation value of false to true. Is there a property setting I can change to globally set lazy="false" unless specified? This would make my upgrade path SOOO much simpler.

start by reading the hibernate migration guide on the wiki....

and look for default-lazy

You know, I found this before, and obviously missed the last line...

*********Migration guide***********
Association fetching strategies

Since it is best practice to map almost all classes and collections using lazy="true", that is now the default. Existing applications will need to explicitly specify lazy="false" on all non-lazy class and collection mappings.

The outer-join attribute is deprecated. Use fetch="join" and fetch="select" instead of outer-join="true" and outer-join="false". Existing applications may continue to use the outer-join attribute, or may use a text search/replace to migrate to use of the fetch attribute.

Beware, this means you have to put lazy="false" on all collection-mappings and classes which previously did not have a "lazy"-attribute.

A quick and dirty alternative for migration is also to put default-lazy="false" on all your hibernate-mapping elements.

That doesn't really help us in our situation. We are using XDoclet and it creates a single hibernate mapping file per class. So, I have to have a lazy="false" in every class (we don't manipulate the hibernate-mapping element that is created by xdoclet). Why not have a single property that can be set in a properties file? Just seems useful, well, at least better than me editing 75 classes adding lazy="false" to each one...

Also, now I get this in my log files:
ERROR main:(org.hibernate.tuple.entity.PojoEntityTuplizer:136) - Getters of lazy classes cannot be final.

Umm, I get this in about 40 different places. I'm assuming I can't just "ignore" it?

You may override the XDoclet template that is used to generate your mappings. Just extract the hibernate.xdt file from the XDoclet JAR and customize it to fit your needs (then include it on the classpath).