[Nanning-developer] new features: AOP Alliance interfaces and multiple interfaces per Mixin

These are two features I've been thinking about for a while.

Multiple interfaces per Mixin
There's no point having just a single interface per mixin, a mixin could 
implement several interfaces. This is also for better compatability with 
PicoContainer. This will probably mean that Mixin.setInterfaceClass and 
Mixin.getIntefaceClass gets replaced by:
boolean Mixin.addInterfaceClass(Class) - returns true if the interface 
didn't already exist
boolean Mixin.removeInterfaceClass(Class) - returns true if interface 
existed before
Collection Mixin.getInterfaceClasses()
boolean Mixin.isImplementing(Class) - utility class to check whether the 
mixin implements the interface

AOP Alliance interfaces
I'm one of the founding members of the AOP Alliance so it's kind of 
stupid that I don't actually implement them. I will implement these 
interfaces and hopefully it could mean we can use some of the 
interceptors from the Spring Framework!

These changes will probably disturb backwards-compatability. (I'm 
thinking specifically about you guys at Lecando.) Please evaluate the 
impact of these changes and report back how I can make the process work 
as good as possible.

I will create these issues in Jira.



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html