[jboss-jira] [JBoss JIRA] Resolved: (JBMICROCONT-270) AbstractKernelDeployer needs to establish KernelDeployment class loader as TCL
[ http://jira.jboss.com/jira/browse/JBMICROCONT-270?page=all ]
Scott M Stark resolved JBMICROCONT-270.
---------------------------------------
Fix Version/s: (was: JBossMC-2.0.0.Beta11)
Resolution: Rejected
The tcl in effect is actually the bootstrap-beans.xml BootstrapClassLoader. Was confused
by it being a org.jboss.system.NoAnnotationURLClassLoader. The bean class loader is
established later during the install callouts. The current jbossas issue is an mbean tcl
issue.
AbstractKernelDeployer needs to establish KernelDeployment class
loader as TCL
------------------------------------------------------------------------------
Key: JBMICROCONT-270
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-270
Project: JBoss MicroContainer
Issue Type: Bug
Affects Versions: JBossMC-2.0.0.Beta11
Reporter: Scott M Stark
Assigned To: Scott M Stark
Priority: Blocker
With the JBDEPLOY-7/JBMICROCONT-231 change to the DeployerWrapper, deployer beans are not
seeing the correct registration class loader. The current usage where the problem is seen
in the bootstrap of the server that loads the bootstrap-beans.xml.
The bootstrap-beans.xml KernelDeployment has its own class loader that refers to the
server libs jars, but this is not seen as the TCL for the deployer beans in
bootstrap-beans.xml. AbstractKernelDeployer.deploy(final KernelDeployment deployment)
should be establishing the deployment.classloader as the TCL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira