> | Is there any chance I can bend Tapestry to advise the implementation class as well?
> Only if you change Tapestry-IoC to copy the annotations from service implemention methods to the corresponding methods in the proxy created for this service. Unfortunately, I don't > have the bytecode knowledge to do it myself and Howard, which does, doesn't like the idea. Same as the good old jmock discussion. Mocking classes is evil. Yeah and when we did we liked it. It feels so unnatural not being able to advise implementation methods. 2013/8/24 Thiago H de Paula Figueiredo <[email protected]> > On Sat, 24 Aug 2013 07:07:51 -0300, Martin Kersten < > [email protected]> wrote: > > Hi there, >> > > Hi! > > I found this example page: >> http://tapestry.apache.org/**using-tapestry-with-hibernate.**html<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? >> > > Tapestry-IoC doesn't support that in services, just in page, component and > mixin classes. > > > 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. >> > > Me too. > > > When I take a look about the Decorator class and the methods called >> it boils down to AspectDecoratorImpl method: >> > > When you define a service without defining an interface, advice isn't > applied to its methods. > > > 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? >> > > Yep. > > > Is there any chance I can bend Tapestry to advise the implementation >> class as well? >> > > Only if you change Tapestry-IoC to copy the annotations from service > implemention methods to the corresponding methods in the proxy created for > this service. Unfortunately, I don't have the bytecode knowledge to do it > myself and Howard, which does, doesn't like the idea. > > -- > Thiago H. de Paula Figueiredo > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > >
