Thiago H de Paula Figueiredo wrote > > On Tue, 22 May 2012 14:19:28 -0300, bhorvat <horvat.z.boris@> > wrote: > >> So tapestry now replaces the need for OSIVF, right? > > tapestry-hibernate and tapestry-jpa solve the same problem as OSIVF but > without using a filter. Instead, it uses perthread services. > >> So if I use spring then I dont need this CommitAfter. > > Yep. You'll use Spring's @Transactional and you'll ned the OSIVF. >
Hi Thiago you are always very helpful I really appreciate that :) So is there solution that implements the best of both worlds. Something that would help me avoid OSIVF but have some transactional functionality that I can put in some higher level method. So I have a method that says addItem and in there I need to save and update a bunch of different entities. The thing is I have tried puting @CommitAfter on methods like that but it didn't work in cases I am trying to delete a bunch of entities. Cheers -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-Transactions-tp5713299p5713330.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
