ansaurus

Question

JPA - Lazy Loading - LazyInitializationException - When Not accessing child collection

Answer 1

A:

Are you sure that you don't access the collection in the toString, hashCode or equals-methods? The later 2 could be used by hibernate to add the results to its cache.

Kurt Du Bois 2010-08-06 06:29:41

No I don't - of course the child object (paperofferingassessment) uses the paperoffering in the hashcode and equals but would that cause a problem - still same issue about why is it instantiated at all

Mark 2010-08-07 08:43:39

Answer 2

A:

Lazy means that collection items will be loaded when someone will call get(index) or other method which needs to operate with fully initialized collection. size() doesn't initialize collection.

You error means, that your code, which tries to get element from collection, working outside from Hibernate session. Session was closed some time before so you get lazy detached collection.

Please, check that you code which operates with collection is executed within transaction. Maybe, yoiu'll need to mark your method with @Transactional annotation (if you using declarative description) or place you code within

TransactionManager tm = //get TransactionManager
try {
    tm.begin();
    //your code
    tm.commit();
} catch (Exception e) {
    tm.rollback();
}

Vadeg 2010-08-31 06:17:30

ansaurus

tags:

views:

answers:

JPA - Lazy Loading - LazyInitializationException - When Not accessing child collection

related questions