View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820639#3820639
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820639 Was thinking about how to scope advice bindings. Currently if you have two versions of the same class loaded by different classloaders, JBoss AOP will apply the same advice bindings to both of those different versions. It would be extremely useful to be able to scope how advice bindings are resolved on a per component/classloader basis. My thinking is a new interface public interface ClassLoaderDomain { public String getDomainName(); } Customer ClassLoaders would implement this interface so that jboss-aop.xml could reference them from with XML. ... bindings... Then you could scope advice bindings per ClassLoader. YOu need the interface because there is no way of identifying a ClassLoader outside of the VM. Inside you can only identify via an address comparison. For running within JBoss, the domain would pertain to a LoaderRepository ObjectName and a UnifiedClassLoader would implement the ClassLoaderDomain interface. Actually, come to think of it, you would need the ability to define multiple domains: Bill ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
