[
https://jira.jboss.org/jira/browse/JBDEPLOY-63?page=com.atlassian.jira.pl...
]
Adrian Brock closed JBDEPLOY-63.
--------------------------------
Resolution: Done
This involves a new deployer that needs configuring in
jboss's conf/deployers.xml
<bean name="ClassLoaderClassPathDeployer"
class="org.jboss.deployers.vfs.plugins.classloader.VFSClassLoaderClassPathDeployer"/>
Split out the Classpath logic into a seperate deployer
------------------------------------------------------
Key: JBDEPLOY-63
URL:
https://jira.jboss.org/jira/browse/JBDEPLOY-63
Project: JBoss Deployers
Issue Type: Task
Components: classloading
Reporter: Adrian Brock
Assignee: Adrian Brock
Fix For: JBDEPLOY-2.0.0.CR1
The ClassPath handling is getting a bit messy because of its "lazy" nature
and having to look across differnt deployment units.
I'm going to break out the classpath determination into a seperate deployer
that runs before the classloader describe deployer to make it cleaner.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira