On Fri, Oct 25, 2013 at 10:53 AM, Barry Books <trs...@gmail.com> wrote:
While it's true you can run into problems by nesting @CommitAfter the same > can be said about nesting any commits. The Tapestry database model is > simple. There is one connection per request and when you call commit it > does a commit. > <pedantic> Tapestry itself doesn't have any database model. It's a web framework and nothing else. You can use it with any database, including none. Tapestry-Hibernate is a package that provides *simple* support for Hibernate and should be used in *simple* scenarios. If you need something that's not simple, like any transaction handling not supported by @CommitAfter, use Tapestry and some transaction handler (EJB, Spring-TX, etc) but not Tapestry-Hibernate. </pedantic> > > > On Fri, Oct 25, 2013 at 7:31 AM, Lance Java <lance.j...@googlemail.com > >wrote: > > > I'm assuming a fork is broken too because it's no good for eating soup? > > Sounds like you need a spoon, it's easy to write your own annotation... > > Perhaps you want a @MaybeCommitAfter ;) > > > -- Thiago
