The class loader should already be defined for all deployers other than class loading
deployers and access via the
DeploymentUnit.getClassLoader/DeploymentContext.getClassLoader. A class loading deployer
should have already run and built the class loader from the classpath(or overriding
metadata).
The point of removing the class loader construction out of base functionality of each
deployer was to allow for more control over the class loading implementation and
integration with deployment lifecycle issues.
However, most deployers are still creating child class loaders of the
DeploymentUnit/DeploymentContext class loader, or creating the own class loader just using
the DeploymentUnit/DeploymentContext classpath. Extracting this aspect is still a work in
progress.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984064#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...