[
https://issues.jboss.org/browse/JBOSGI-447?page=com.atlassian.jira.plugin...
]
Thomas Diesler commented on JBOSGI-447:
---------------------------------------
Although technically possible, I don't see why a bundle would need a dynamic import on
core packages.
How does Equinox behave WRT this?
I'd say a bundle that uses a BundleActivator should fail to resolve if it does not
import org.osgi.framework
It should still fail if it uses Dynamic-ImportPackage=*
At this stage I'd rather be strict. When we have a customer issue, we can revisit.
Dynamic-ImportPackage=* fails for org/osgi/framework
----------------------------------------------------
Key: JBOSGI-447
URL:
https://issues.jboss.org/browse/JBOSGI-447
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Affects Versions: JBossOSGi 1.0.x
Reporter: David Bosschaert
Attachments: weld-osgi-impl-1.0-SNAPSHOT.jar
I came across a bundle that has a Dynamic-ImportPackage: * but deploying this in AS7
causes a NoClassDefFoundError on org.osgi.framework.BundleActivator.
I would argue that the design of this bundle could be improved to at least explicitly
import org.osgi.framework, but it should work. This bundle works fine in Apache Felix.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira