[
http://jira.jboss.com/jira/browse/JBVFS-3?page=all ]
Dimitris Andreadis moved JBMICROCONT-158 to JBVFS-3:
----------------------------------------------------
Project: JBoss VFS (was: JBoss MicroContainer)
Key: JBVFS-3 (was: JBMICROCONT-158)
Component/s: (was: VFS)
Fix Version/s: 2.0.0.Beta7
Affects Version/s: (was: JBossMC_2_0_0 Beta3)
Non-existent manifest Class-Path refs produce vfs
IllegalStateException
-----------------------------------------------------------------------
Key: JBVFS-3
URL:
http://jira.jboss.com/jira/browse/JBVFS-3
Project: JBoss VFS
Issue Type: Bug
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: 2.0.0.Beta7
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.
--
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