for some reason my many-to-one objects refuse to lazy load. rather when the parent is created all child objects are fetched with separate sql statements immediately. all the child objects have lazy="true". is there something missing here?

You are surely accessing the collection somewhere, perhaps in the setter. Use your debugger.

I know for a fact that i am not accessing any fields from any of the many-to-one objects. i turned on the debug and looked at the output and i am still not sure why it is forcing the associations to be lookedup. here is a little of the debgu output:

first the sql for the main object is run then....

14:29:06,814 DEBUG SessionImpl:2202 - resolving associations for [edited/myobject#9000]
14:29:06,814 DEBUG SessionImpl:1986 - loading [edited/mysubobject#2500]
14:29:06,844 DEBUG SessionImpl:1986 - loading [edited/mysubobject2#12906]
14:29:06,844 DEBUG SessionImpl:3933 - creating collection wrapper:[edited/mysubcollection#9000]
14:29:06,864 DEBUG SessionImpl:2226 - done materializing entity [edited/myobject#9000]
14:29:06,864 DEBUG SessionImpl:3116 - initializing non-lazy collections
14:29:14,601 DEBUG SessionImpl:2083 - attempting to resolve [edited/mysubobject#2500]
14:29:14,611 DEBUG SessionImpl:2116 - object not resolved in any cache [edited/mysubobject#2500]
14:29:14,611 DEBUG EntityPersister:416 - Materializing entity: [edited/mysubobject#2500]

after this the sql for subobject1 and subobject2 are ran.

Is your collection really mapped with lazy="true"? You know, for example posting the relevant parts of your mapping would surely get you better answeres faster.

ok.
here is the relevant part from the parent object:

<many-to-one name="agent" column="DB_BP_CSR_ID" class="Agent" outer-join="auto" />

here is the relevan part from the child object:

<class name="Agent" table="TBL_AGENCY_USER" lazy="true">

also, the agent object has two more child object. these children are not loaded when the parent is. only this agent object seems to want to load.


shane

You're not doing any funky toString()'ing of objects for debugging purposes, are you? (Or any other usage of collections)

We had this problem once and it was caused by a naively written toString() method, so when you debugged the parent object a side-effect was that the children collections were loaded.

This is quite nasty when you realise that having debugging turned on/off can affect the behaviour of your app (ie. when children objects are loaded). It can be especially nasty with detached objects, results in issues like "when debug is off, we get LaziInitialization exceptions").