I am not sure, never used Tapestry transaction support, but if you want full transaction support, use JEE
On Nov 29, 2012, at 5:06 PM, Pillar <sotodel...@hotmail.com> wrote: > More questions: > > I have an onSuccess() method in my Page class that calls a DAO delete method > annotated with @CommitAfter. When the onSuccess() gets called (I'm using a > form with a submit) the delete doesn't get commit at the end of the request > (although I see hibernate log it). If I annotate the onSuccess() method with > @CommitAfter, then the delete is commit and the entity is no longer in my > db. Is this what you meant by doesn't support nesting? What is up? > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/CommitAfter-not-committing-my-transaction-tp5718364p5718407.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
