[jboss-jira] [JBoss JIRA] Resolved: (JBVFS-102) Creating a VFSRoot on a Jar Entry and subsequently opening the VirtualFile via it's URL fails
Ales Justin (JIRA)
jira-events at lists.jboss.org
Mon May 11 05:35:48 EDT 2009
[ https://jira.jboss.org/jira/browse/JBVFS-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ales Justin resolved JBVFS-102.
-------------------------------
Fix Version/s: 2.1.1.GA
Resolution: Done
> Creating a VFSRoot on a Jar Entry and subsequently opening the VirtualFile via it's URL fails
> ---------------------------------------------------------------------------------------------
>
> Key: JBVFS-102
> URL: https://jira.jboss.org/jira/browse/JBVFS-102
> Project: JBoss VFS
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 2.1.0.GA
> Reporter: Carlo de Wolf
> Assignee: Ales Justin
> Priority: Critical
> Fix For: 2.1.1.GA
>
>
> java.io.IOException: Child not found META-INF/MANIFEST.MF/META-INF/MANIFEST.MF for JarHandler at 18163514[path= context=jar:file:/home/carlo/work/jboss-vfs/target/test-classes/vfs/test/jar1.jar!/ real=jar:file:/home/carlo/work/jboss-vfs/target/test-classes/vfs/test/jar1.jar!/], available children: [JarEntryHandler at 29524641[path=META-INF context=jar:file:/home/carlo/work/jboss-vfs/target/test-classes/vfs/test/jar1.jar!/ real=jar:jar:file:/home/carlo/work/jboss-vfs/target/test-classes/vfs/test/jar1.jar!/!/META-INF/], JarEntryHandler at 17707667[path=org context=jar:file:/home/carlo/work/jboss-vfs/target/test-classes/vfs/test/jar1.jar!/ real=jar:jar:file:/home/carlo/work/jboss-vfs/target/test-classes/vfs/test/jar1.jar!/!/org/]]
> at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:461)
> at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.resolveVirtualFile(VirtualFileURLConnection.java:106)
> at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getVirtualFile(VirtualFileURLConnection.java:118)
> at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:93)
> at java.net.URL.openStream(URL.java:1027)
> at org.jboss.test.virtual.test.JarFileURLTestCase.test1(JarFileURLTestCase.java:53)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:232)
> at junit.framework.TestSuite.run(TestSuite.java:227)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list