[jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: Modularising the appserver bootstrap

[adrian@jboss.org]

"adrian at jboss.org" wrote : 
  | The fix would to refactor the VFSClassLoaderScopingPolicy
  | such that the deployment logic is in the deployers which just invoke the
  | registerClassLoader()
  | 
  | i.e. remove its dependency on the deployment layer
  | 

Additionally, I think the logic in this code is a bit dated?

With the new classloader, it is not just wars that can have their own isolated classloaders.
Any subdeployment with its own classloading metadata can create a sub-module
in its own classloader domain.

And even wars don't necessarily have an isolated classloader, this is just a default rule,
i.e. we add a classloading metadata to all wars that don't have an explicit one 
to put them in their own classloader domain.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176520#4176520

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176520