Dynamically changing the Lazy option

Kasi · **Joined:** Wed May 17, 2006 1:44 pm **Posts:** 6

Code:

 Configuration conf = getConfig();
        Iterator it = conf.getClassMappings();
        while (it.hasNext()) {
            org.hibernate.mapping.PersistentClass cl = (org.hibernate.mapping.PersistentClass) it.next();
            cl.setProxyInterfaceName(cl.getEntityName());
            cl.setLazy(false);
        }
        setSessionFactory(conf.buildSessionFactory());

All my Hbm.xml files are set default-lazy = "true"

In the code i amsetting lazy is false. But its not working..Its not returning data properly.
Can any one help me
thanks
Kasi

tenwit · **Joined:** Thu Dec 23, 2004 9:08 pm **Posts:** 2008

In what circumstances? default-lazy applies only in certain circumstances (hence "default" as opposted to "override" or "always"). It works when using Session.get/load, or when you've loaded an object with an assoication to the class in question, but not when you're querying the class directly via criteria or HQL.

Kasi · **Joined:** Wed May 17, 2006 1:44 pm **Posts:** 6

Thanks a lot. Thats really good to know. Can you please let me know where can i find those kind of documentation. I really appreciate if you let me know the documentation.
Thanks
Kasi

tenwit · **Joined:** Thu Dec 23, 2004 9:08 pm **Posts:** 2008

As with many hibernate features, to figure out exactly what it means you have to read the entire ref docs, and lots of sample code. From refdocs section 6.1.2:

Quote:

default-lazy (optional - defaults to true): The default value for unspecifed lazy attributes of class and collection mappings.

So all it does it set lazy="true" anywhere that allows a lazy="" attribute but doesn't have one.

From refdocs section 20.1.2:

Quote:

The fetch strategy defined in the mapping document affects:

* retrieval via get() or load()
* retrieval that happens implicitly when an association is navigated (lazy fetching)
* Criteria queries

Note that HQL is not in this list.

And of course, experience and experimentaiton fills in the gaps in the docs. I can't find anything in the refdocs that explicitly says that critieria (usually?) ignore the lazy attributes in your mapping file, but I know that they do.

FYI, default-lazy="true" is the default (up to 3.0.. I think it's default-lazy="no-proxy" in newer releases, not certain). So you don't strictly need to put that in your mapping files, though it doesn't hurt and does serve in a sort of self-documenting role.

nag · **Joined:** Tue Nov 08, 2005 1:30 pm **Posts:** 50

thanks