i am using hibernate 3.0.3.

i have a mappinig file for class Business which has two one-to-many associations as follows:

<set name="contacts" cascade="all-delete-orphan">
<key column="BUSINESS_ID"/>
<one-to-many class="Contact"/>
</set>
<set name="addresses" cascade="all-delete-orphan">
<key column="BUSINESS_ID"/>
<one-to-many class="Address"/>
</set>

i use Criterial API for eager fetching Business instances as follows:

Example exampleBusiness = Example.create(example).ignoreCase().enableLike(MatchMode.ANYWHERE);
Criteria crit = getSession().createCriteria(Business.class).add(exampleBusiness);
crit.setFetchMode("contacts", FetchMode.JOIN );
crit.setFetchMode("addresses", FetchMode.JOIN );
return crit.list();

howoever, i always got failed lazy initializastion error as follows:

ERROR LazyInitializationException:19 - failed to lazily initialize a collection (Business.addresses) - no session or session was closed

i looked at the generated SQL statement, there was no outer join with Address. what is more puzzling to me is that in the mapping file for Business, if i move association addresses ahead of contacts as follows:

<set name="addresses" cascade="all-delete-orphan">
<key column="BUSINESS_ID"/>
<one-to-many class="Address"/>
</set>
<set name="contacts" cascade="all-delete-orphan">
<key column="BUSINESS_ID"/>
<one-to-many class="Contact"/>
</set>

then i get lazy initialization error complaining about contacts not being initialized.

could some experts out there shed some light on this? did i do something wrong.

thanks very much!

pete

any help is very much appreciated!

regards, pete

hi

i had similar problems with hibernate 3.1 and i fixed it by doing this stupid code:



i think the list() is broken when used with ALIAS_TO_ENTITY_MAP
hope it helps someone!

fabian