No. Only the page classes.
I'm not too worried about it, Thiago says not-supported.
It's just a change in behaviour from 5.3.7 to 5.4-beta. The concern I am
more interested in raising is the stack trace on the command line is not
there where I'm running from but it's caught by tapestry.
If time
Is the service also annotated with @CommitAfter? This could cause a nested
transaction.
OK. ever ;) I didn't know what nested transactions were in hibernate.
Just a change in behaviour from 5.3.7 to 5.4
My bastardised workflow likes to use tapestry-hibernate for doing the UI
and then porting to EJB.
On Wed, Aug 27, 2014 at 11:47 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.co
On Wed, 27 Aug 2014 10:07:59 -0300, Lance Java
wrote:
I'm not sure what you mean by nesting db queries? Can you give an
example?
Note, the @CommitAfter annotation does exactly what it says on the tin,
it causes a commit after every method that has the annotation.
And no tapestry-hibern
hm
I'm guessing it's when there are 2 or more saves to DB from a method.
Nothing in the stack trace shows errors at all, but I get the tapestry
exception page with:
org.apache.tapestry5.ioc.internal.OperationException
*nested transactions not supported*
onSuccess() method just looks lik
I'm not sure what you mean by nesting db queries? Can you give an example?
Note, the @CommitAfter annotation does exactly what it says on the tin, it
causes a commit after every method that has the annotation.
