Details
-
Bug
-
Resolution: Done
-
Major
-
EAP 5.0.1
-
None
-
-
Workaround Exists
-
Description
The LegacyDeploymentContextComparator requires that it's create() method be called to be properly initialized. However, it is used by the EARStructureDeployer bean (configured in the <jboss-home>/server/<server-dir>/deployers/ear-deployer-jboss-beans.xml) which makes no such lifecycle assumption. By default, this works because the LegacyDeploymentContextComparator is instantiated as an MC bean (topContextComparator) in <jboss-home>/server/<server-dir>/conf/bootstrap/deploy.xml causing it's create() method to be called as part of the MC bean lifecycle. However, if the topContextComparator is replaced by, for example, the LegacyPrefixDeploymentContextComparator, use of the LegacyDeploymentContextComparator by the EARStructureDeployer can lead to a NPE during EAR deployments. (See discussion on JBAS-7614.)
Attachments
Issue Links
- is related to
-
JBAS-7614 Implementing PrefixDeploymentSorter feature in JBoss5.
- Closed