"kabir.khan(a)jboss.com" wrote :
org.jboss.aop.asintegration.jboss5.AOPClassLoaderDeployer is set up in AS to do this.
|
| It calls AOPClassLoaderInitializer.initializeForUnit() which in turn ends up in
DomainRegistry.initMapsForLoader()
Yes, but that's something AOP-related. I want to have an approach that is independent
of JBoss AOP. I plan to split that DomainRegistry related stuff away from AOP, as it is
now a classpool related thing (the new AOP impl that uses the classpool project contains
already a split, but I think I'll work some more on that before considering it done).
Do you think that using a deployer for only calling DomainRegistry.initMapsForLoader is
appropriate? I see that AOPClassLoaderDeployer adds the AspetManager as an attachment to
the unit, which IMO justifies the need for a deployer. But I'm not sure about a
deployer that is only used for calling initMapsForLoader.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264319#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...