I would leave everything as is now. Tapestry should not try to implement or re-implement full transaction support. This has already been done with JEE or spring. If a user wants this support, they should just use what already exists out there.
On Aug 24, 2013, at 3:18 PM, "Thiago H de Paula Figueiredo" <thiag...@gmail.com> wrote: > On Sat, 24 Aug 2013 09:39:11 -0300, Taha Siddiqi <tawus.tapes...@gmail.com> > wrote: > >> Hi everyone > > Hi! > >> There are two @CommitAfters and both work differently from each other. > > This is a problem > > Here's my suggestion: > > 1) Leave the @CommitAfter implementations the way they are now for > backward-compatibility reasons. > 2) Mark them as deprecated. > 3) Use EJB's @TransactionAttribute annotation instead of tapestry-hibernate > and tapestry-jpa defining different annotations. > 4) Implement the different transaction attribute types described in > http://docs.oracle.com/cd/B32110_01/web.1013/b28221/servtran002.htm. > > Question: use JTA? I don't know. > > -- > Thiago H. de Paula Figueiredo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
