I run a lot of batch transactions and I use @Inject and @CommitAfter without any problems so I don't think they are the issue. For high volumes I usually use plain SQL though because it's easier to control.
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. 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 ;) >
