I think you should. It looks like Tapestry is having the problem displaying the error page. You have the conditional for outside the ifLoggedIn check. Out of curiosity, what happens if that is moved inside the ifLoggedIn check?
I'm wondering if the Acegi RememberMe filter is putting a detached Hibernate object into the HTTP Session that Tapestry is trying to display on an error page, thereby triggering the exception. So you would be seeing the error because you are triggering another error... or not ;-) Jonathan > -----Original Message----- > From: zack.manning [mailto:[EMAIL PROTECTED] > Sent: Monday, July 07, 2008 14:40 > To: users@tapestry.apache.org > Subject: RE: LazyInitializationException for ASO? > > > Yea that seems to have done it. Shouldnt I be able to just check if the > ASO > is null? Every @ApplicationState of mine is set create = false. I might > use that other places in the app and just want make sure I know the cause > of > the error so it doesnt crop up elsewhere. > > Zack > > > Jonathan Barker wrote: > > > > > > Are there any places where you use the @ApplicationState annotation for > > Survey or Project without create=false? > > > > What happens if you test on "surveyExists" which would be the way before > > the > > create=false option was introduced? > > > > > > -- > View this message in context: > http://n2.nabble.com/LazyInitializationException-for-ASO-- > tp363398p363430.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
