Hi there,
I found this example page:
http://tapestry.apache.org/using-tapestry-with-hibernate.html.
The problem I have are these lines:
package com.example.tutorial.pages.address;....public class CreateAddress {
...
@CommitAfter
Object onSuccess() {
...
}
}
Is it possible to annotate non-interface methods? How is that?
I am still struggling with @CommitAfter and all this. I would love to
annotate
the Implementation class instead of the service interface which seams more
obvious to me, since the transactional behavior is part of the
implementation
not the definition.
When I take a look about the Decorator class and the methods called
it boils down to AspectDecoratorImpl method:
public <T> AspectInterceptorBuilder<T> createBuilder(final Class<T>
serviceInterface, final T delegate,
AnnotationAccess annotationAccess, final String description) {
}
It says serviceInterface and the method used to advice Class.getMethods.
Therefore it would be all methods available.
Digging myself into the swamp of builder and bind, I found that the
serviceInterface seams to be the real provided interface rather then the
implementation class. Am I correct on this?
Is there any chance I can bend Tapestry to advise the implementation class
as well? It
would be create to use @CommitAfter in the implementation class rather then
the interface
where it does not belong to since Transactional behavior is for sure an
Implementation issue
and not about the description of what happends but how.
Cheers,
Martin
