Hey everyone

Here is my problem :

I have a service (service1) that has a method (method1) which has the
@CommitAfter annotation in order for tapestry to take care of the
transaction.
I have a second service (service2) that has a method (method2) which also
has the @CommitAfter annotation.
service2 is injected into service1 and method2 is used by method1.

The problem is method2 commits the transaction even though it is not the
one that began it. Thus, every modifications made to managed entities that
are done after the method2 call in method1 are not commited.

Am i wrong using those services like that or is it the advisor that has a
wrong behavior ?

Thx in advance,
Charles.

Reply via email to