[
http://jira.jboss.com/jira/browse/JBMICROCONT-158?page=comments#action_12... ]
Max Andersen commented on JBMICROCONT-158:
------------------------------------------
Any known workarounds around this ?!
I'm getting this too when I'm trying to run unittests directly from the IDE where
these jars might not yet be packaged up but just be on the global classpath.
Non-existent manifest Class-Path refs produce vfs
IllegalStateException
-----------------------------------------------------------------------
Key: JBMICROCONT-158
URL:
http://jira.jboss.com/jira/browse/JBMICROCONT-158
Project: JBoss MicroContainer
Issue Type: Bug
Components: VFS
Affects Versions: JBossMC_2_0_0 Beta3
Reporter: Scott M Stark
Assigned To: Scott M Stark
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