The only reason we have the OSIV Filter commented out in M5 is so users can easily switch between persistence frameworks. We also don't need it in AppFuse's default features, so it made sense to comment it out. If you run into LazyInitializationExceptions, we recommend you uncomment it or use eager fetching for your objects (or initialize them in your service layer).
Matt On 8/13/07, romsrini <[EMAIL PROTECTED]> wrote: > > Hello, > > I tried the steps enumerated in the upgrade guide of the 2.0 M5 Release > Notes page. Initially, everything seemed to work fine in that all our tests > passed. But, when I ran the application and tried accessing our first page, > I started getting LazyInitialization exceptions like: > > org.hibernate.LazyInitializationException: could not initialize proxy - the > owning Session was closed > > or > > org.hibernate.LazyInitializationException: failed to lazily initialize a > collection of role: com.lexy.model.MenuGroup.children, no session or session > was closed > > I'm able to make these errors go away and make our application work if I > ignore step #17: > "The OpenSessionInViewFilter is now commented out in web.xml by default." > So, if I don't comment out the OpenSessionInViewFilter, everything seems > okay. > > Is there a different fix for this problem in M5? > > > Thanks, > Rom > > > > > > -- > View this message in context: > http://www.nabble.com/2.0-M5-upgrade-issue-tf4263095s2369.html#a12132201 > Sent from the AppFuse - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
