Thanks, that let me in the right direction. I ended up writing my own
class and method matchers that both accepted the same list of
subpackage names as the method matcher can't simply grab the package
names from the class matcher.
In case anyone else is trying to do class matching at runtime,
Hi;
Has anyone worked with the AOP interceptors in Guice much? I'm used
to using full blown AspectJ in my other projects and am having
difficulty reproducing some mix-in behaviour using plain AOP.
I want to introduce a tracer on instance methods in certain packages.
The catch is that I only
Notice the first Matcher takes a ? super Class and it decides if the
class is eligible for AOP. The second Matcher takes a ? super Method
and it decides if it should intercept the method or not.
Nothing is stopping you from inspecting the method e.g.
new AbstractMatcherMethod() {
