[jboss-osgi-issues] [JBoss JIRA] Moved: (JBOSGI-459) URL.openStream() on URL returned from bundle.getResource() returns a zero-byte stream
Thomas Diesler (JIRA)
jira-events at lists.jboss.org
Thu Jun 2 05:14:01 EDT 2011
[ https://issues.jboss.org/browse/JBOSGI-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Diesler moved AS7-937 to JBOSGI-459:
-------------------------------------------
Project: JBoss OSGi (was: Application Server 7)
Key: JBOSGI-459 (was: AS7-937)
Workflow: jira (was: GIT Pull Request workflow )
Affects Version/s: JBossOSGi 1.0.0 Beta10
(was: 7.0.0.CR1)
Component/s: (was: OSGi)
Security: Public
> URL.openStream() on URL returned from bundle.getResource() returns a zero-byte stream
> -------------------------------------------------------------------------------------
>
> Key: JBOSGI-459
> URL: https://issues.jboss.org/browse/JBOSGI-459
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossOSGi 1.0.0 Beta10
> Reporter: David Bosschaert
> Assignee: David Bosschaert
> Attachments: org.apache.aries.spifly.examples.provider1.bundle-0.4-SNAPSHOT.jar, org.apache.aries.spifly.examples.spi.bundle-0.4-SNAPSHOT.jar
>
>
> The attached bundle contains an embedded jar file which is referenced to by the Bundle-ClassPath.
> Calling bundle.getResource("org.apache.aries.spifly.examples.provider1.jar-0.4-SNAPSHOT.jar") does return a URL.
> {code}bundle.getResource("org.apache.aries.spifly.examples.provider1.jar-0.4-SNAPSHOT.jar")
> (java.net.URL) bundle://org.apache.aries.spifly.examples.provider1.bundle-22-0-0/org.apache.aries.spifly.examples.provider1.jar-0.4-SNAPSHOT.jar/{code}
> but opening that URL and reading the bytes yields 0 bytes.
> This only seems to be an issue with URLs that refer to jar files. Other resources are readable without problems.
> BTW this works fine on Equinox and Felix.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-osgi-issues
mailing list