Does seem a little inconsistent. Raise a bugzilla to track clarifying why it is the right behaviour or fixing it.
Andy 2009/8/27 Simone Gianni <[email protected]>: > Hi all, > I don't know if this is a bug, or if it's a known or wanted behavior, but > using after() returning(Object o) on a set() pointcut does not weave it. > > Since documentation states that using Object in the returning clause will > match also methods returning void, which it does, I would expect it to weave > correctly also set() pointcuts, which obviously return "void". > > A normal after() advice (without the returning clause) will match and weave > correctly, but makes it necessary to write the advice twice if I'm willing > to trace all execution, get() and set() to trace an execution. > > This is happening under 1.6.5, both LTW and CTW, both from inside AJDT and > from command line. > > Simone > > -- > Simone Gianni CEO Semeru s.r.l. Apache Committer > http://www.simonegianni.it/ > > _______________________________________________ > aspectj-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/aspectj-users > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
