That part is OK... @CommitAfter works for other methods.
2014-10-24 16:16 GMT+02:00 George Christman <gchrist...@cardaddy.com>:
> If I'm not mistaking you need to advice tapestry of it and the annotation
> will need to reside in your interface. I'm not sure if that changed in 5.4.
> I added the following code to my app module to get it to work with my
> DAO's.
>
> @Match("*DAO")
> public static void adviseTransactions(HibernateTransactionAdvisor
> advisor, MethodAdviceReceiver receiver) {
> advisor.addTransactionCommitAdvice(receiver);
> }
>
> On Fri, Oct 24, 2014 at 10:10 AM, Charlouze <m...@charlouze.com> wrote:
>
> > Hey everyone,
> >
> > I'm facing an issue with @CommitAfter annotation being placed on
> > implementation.
> >
> > I have 2 interfaces A and B :
> >
> > public interface A<T> {
> > void methodA(T t);
> > }
> >
> > public interface B extends A<C> {
> > void methodB();
> > }
> >
> > and one implementation BImpl :
> >
> > public class Bimpl implements B {
> > @Annotated
> > void methodA(C t){...}
> >
> > void methodB(){...}
> > }
> >
> > The annotation @Annotated is not present in MethodInvocation at runtime.
> I
> > suspect it to be because of the generic parameter of interface A.
> >
> > Is there or bug or am I using this the wrong way ?
> >
> > Charles
> >
>
>
>
> --
> George Christman
> www.CarDaddy.com
> P.O. Box 735
> Johnstown, New York
>
