Initializing lazy associations

rsr · **Posted:** Mon Dec 08, 2003 12:17 pm

Hello,

I have the associations below:

Code:

A <----> B (A->B = one-to-many, lazy=true), (B->A = many-to-one)
A <----> C (A->C = one-to-many, lazy=true), (C->A = many-to-one)
A <----> D (A->D = one-to-many, lazy=true), (D->A = many-to-one)
A <----> E (A->E = one-to-many, lazy=true), (E->A = many-to-one)
E <----> F (E->F = one-to-many, lazy=true), (F->E = many-to-one)

Because I'm working with a session disconnected from the view tier, I need to initialize the collections on DAO tier. To load the object "A" without load "F" I do this:

Code:

List result = session.find("from A");
Iterator ite = results.iterator();
while (ite.hasNext()) {
       A a = (A) ite.next();
       Hibernate.initialize(a.getBs());
       Hibernate.initialize(a.getCs());
       Hibernate.initialize(a.getDs());
       Hibernate.initialize(a.getEs());
}

Is there a better way to do this job?

Thanks!

emmanuel · **Posted:** Mon Dec 08, 2003 12:21 pm

remove lazy=true ;-)

rsr · **Posted:** Mon Dec 08, 2003 12:31 pm

cardin · **Posted:** Mon Dec 08, 2003 1:18 pm

In this case, would it make sense to have a separate configuration for "remoting" of objects?

Meaning, one configuration in which you do business code on the server, with lazy loads all over the place.

When it's time to go to the other tiers, you use a configuration that has everything eager...

Experts ?

emmanuel · **Posted:** Mon Dec 08, 2003 2:06 pm

I personaly apply the 80%-20% rule. if BCD are needed 80% of your request then not lazy.
If BCD is needed 20% or less time then initialize is goods enough and more simple.

Quote:

In this case, would it make sense to have a separate configuration for "remoting" of objects?

Hum, lot's of pain and probably extra DB use since every request need to be executed twice... (1 for business mgt, and 1 for rendering). Whatever, duplicating mapping and managing 2 sessions and 2 sessionFactories is more or less a showstopper to me (2-PC Tx headache, ...).