This now is all in the realm of Spring so I don't want to say too much... Essentially, it doesn't matter how many 'nested' method calls you make, [with PROPAGATION_REQUIRED] the transaction will rollback to (and commit at) where the annotation was first encountered.
See the Spring docs for more: http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/html/transaction.html#tx-propagation @Transactional just gives you finer grained control over rollback points and read access. Steve. On 31 May 2012 05:25, bhorvat <horvat.z.bo...@gmail.com> wrote: > Can you elaborate a bit more the part below > > > Steve Eynon wrote >> >> unlike T5's @CommitAfter, it doesn't always commit or start a new >> transaction. >> > > The T5 annotation always commits when there is not RuntimeException so what > does @Transactional annotation does then :S > > tnx > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Tapestry-Transactions-tp5713299p5713540.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
