Yeah, you can put the Spring @Transactional annotation on any Spring bean / service. Both on the class and its methods.
The propagation=Propagation.REQUIRED ensures the code runs inside a transaction but unlike T5's @CommitAfter, it doesn't always commit or start a new transaction. It sounds like this does what you want. Steve. On 25 May 2012 21:33, bhorvat <horvat.z.bo...@gmail.com> wrote: > So you put your transactional annotation on the DAO, right? The CommitAfter > does that for me as well, what I need is to put it on some layer above that > has multiple contats to the couple of different DAOs. One that saves one > part of the transaction, other that saves another but the should fail or > success together, can I do this with you configuration? Can I put > Transactional annotation on something other then HibernateDAO. > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Tapestry-Transactions-tp5713299p5713416.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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
