[
https://jira.jboss.org/browse/JBOSGI-402?page=com.atlassian.jira.plugin.s...
]
David Bosschaert commented on JBOSGI-402:
-----------------------------------------
I managed to get pretty far with this one and put my work on this branch:
http://github.com/jbosgi/jbosgi-framework/tree/jbosgi402_2
It depends on the
http://github.com/jbosgi/jbosgi-resolver/commits/jbosgi404 work being
applied (JBOSGI-404).
There is currently still a failure in one of my new tests:
FragmentTestCase.testFragmentHostCircularDeps(). The test has a circular dependency
between a host and a fragment (host imports package from its own fragment, fragment
imports package from its own host - this is the SLF4J use case). It seems like the
resolver part is going ok with the correct wires being created. However at classloading
time it fails when a class in the fragment implements an interface from the host.
I wonder whether this is caused by the fact that we use a separate classloader for the
fragment (the FragmentLocalLoader) while the spec clearly says: "All class or
resource loading of a fragment is handled through the host’s class loader or Bundle
object, a fragment must never have its own class loader" (4.2 core spec 3.13.2).
Host importing package from Fragment doesn't resolve
----------------------------------------------------
Key: JBOSGI-402
URL:
https://jira.jboss.org/browse/JBOSGI-402
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jboss-osgi-resolver
Affects Versions: JBossOSGi 1.0.0 Beta9
Reporter: David Bosschaert
Assignee: David Bosschaert
Fix For: JBossOSGi 1.0.0 Beta10
This issue arose when splitting up jbosgi-osgi-common into a number of proper bundles.
jbosgi-osgi-common contains
Bundle slf4j.api:
Export-Package: org.slf4j
Import-Package: org.slf4j.impl
There is also the slf4j-log4j12 fragment:
Fragment-Host: slf4j.api
Import-Package: org.slf4j
Export-Package: org.slf4j.impl
See testHostDependsOnFragmentPackage() in
http://github.com/jbosgi/jbosgi-resolver/blob/master/itest/src/test/java/...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira