Feature request: Unique Identifier per Advice application

Given a class like this:

public class Foo {
  public void foo1() {}
  public void foo2() {}
}

If I write advice that instruments each public method in Foo, there is not a simple way to uniquely identify the advice for each method. I suggest something like this:

@Advice.Pointcut int unscopedUniqueIdentifier
@Advice.Pointcut(Foo.class) int fooScopedUniqueIdentifier

I expect this would be implemented via a shared AtomicInteger per the scope provided. The ID could be injected as a constant into the bytecode and probably regenerated each time a retransformation occurs.

The alternative would be to use a combination of class and method name + signature mapping to an ID, but that would be much less performant.

[raphw]

Have a look at the unit tests, they should reflect any possible use case. Other then that, have a look at Mockito. We inject unique ids per mock maker in there. Mockito only defines a hand full of advice, so it should be easy to find by looking for the @Advice annotations there.

[tylerbenson]

Cool. Do you know of any examples you could point me to?