> Say that you > load an object and that object has a list of objects in it, and you try to > access the list in the tml page with say the loop component. Now if you > dont > use the OpenSessionInViewFilter you should get an exception > (LazyInitalization).
> Yes but only if the session is close. But isn't the idea of the OpenSessionInViewFilter to fix the problem that session is closed before tml is starting to render. However even with it everything works fine. So if I have a list of objects and I use it in a loop component I dont get an exception, but I was under the impression that I should get it and in order to fix the problem I should use the OSIVF > However I dont get that exception, so I was wondering > (since most of the stuff for OSIVF is a bit old) is tapestry now handling > this itself (tapestry-hibernate that is) or am I miss understanding what > the > filter is used for in the first place? > > No. So tapestry now replaces the need for OSIVF, right? > Yes . Why is that unusable for you? The LazyInitalization is caused > because > the entity is from another session (detached) and you are trying to access > a lazy property. It would be nice so that I dont have to worry about this. With complex object relationship I can never be too sure if I will get that exception until I run. > CommitAfter is a nice example. But CommitAfter doesn't support nested > transactions. For this you'll need your own advice - or just don't call > @CommitAfter annotated methods in a transaction (other @CommitAfter > methods). So if I use spring then I dont need this CommitAfter. I will have to read more about it :) cheers and tnx for your help -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-Transactions-tp5713299p5713325.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
