@OneToMany(fetch = FetchType.EAGER)



This is a lazy approach, with a cumulatively heavy performance penalty. To really solve Lazy Initialization Exceptions, you need to find out why the Hibernate session closed before you wanted it to, and/or you need to get a new session reattach the object.

Tapestry5AvoidingLazyInitializationExceptions (last edited 2010-12-30 02:18:40 by BobHarner)