-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
Workaround Exists
-
When the structure deployers parse a top-level jboss-test-entity.jar with a manifest like:
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.5
Created-By: 1.5.0_09-b01 (Sun Microsystems Inc.)
Class-Path: ejb.jar jnp-client.jar jboss-client.jar jndi.jar jboss-jmx
.jar junit.jar deploy.jar
it fails with:
Caused by: java.lang.IllegalStateException: JarHandler@28271403[path= context=file:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/jboss-test-entity.jar
real=file:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/jboss-test-entity.jar] has no parent.
at org.jboss.virtual.VFSUtils.addManifestLocations(VFSUtils.java:116)
at org.jboss.deployers.plugins.structure.DefaultStructureBuilder.processContext(DefaultStructureBuilder.java:131)
at org.jboss.deployers.plugins.structure.DefaultStructureBuilder.populateContext(DefaultStructureBuilder.java:89)
The invalid references should at most produce debug level warnings.