PackageAdmin doesn't list [Resolved] bundle packages.

[ebelanger070]

Using JBoss 7.1.2.Final (built from source)

Greetings,

I am still in the progress of evaluating JBoss AS 7.1 in replacement of Eclipse Equinox.  I had an unexpected behavior with a fragment bundle and after some testing, may have found a bug.  Using PackageAdmin, I tried to lookup a provided package from a bundle.  The package was not available.  I then queried the bundle state, which was RESOLVED.  Just for test, I activated the bundle and the package was then available.

I get a different behavior when using Equinox PackageAdmin implementation.  PackageAdmin.getExportedPackage() will actually retrieve exported packages in RESOLVED bundles.  This behavior is even more important with fragments.  Fragments cannot be ACTIVE and will stay in a RESOLVED state.  This means the fragments can provide packages in Equinox.  This doesn't seem to be the case with JBoss.

In summary,  Equinox PackageAdmin will detect packages in bundles with RESOLVED state, JBoss PackageAdmin doesn't seem to.  Also, fragments are RESOLVED at most, which means that fragments packages cannot be resolved in JBoss.

As always, thank you for your answers and if you need more information or collaboration on my part, do not hesitate to ask.

[thomas.diesler]

Ok thanks - I'll have a look. Please monitor

https://issues.jboss.org/browse/JBOSGI-570

In the mean time you might want to add this use case to

Running org.jboss.test.osgi.framework.packageadmin.PackageAdminTestCase

Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.903 sec

or

Running org.jboss.test.osgi.framework.fragments.FragmentTestCase

Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.847 sec

This would help greatly.

git clone git://github.com/jbosgi/jbosgi-framework.git

cd jbosgi-framework

mvn install

[ebelanger070]

Greetings Thomas,

It took some time, but I figured out how to use the test suites and add my own test.  You can look at the file on my github fork.

https://github.com/ebelanger/jbosgi-framework/blob/fragmentExportedPackageTest/itest/src/test/java/org/jboss/test/osgi/framework/packageadmin/PackageAdminTestCase.java

The test in question is testGetFragmentExportedPackage.

I didn't want to open a pull request since I didn't take the time to match the JBoss code standards and I do not know on which branch this fix should be implemented.  So feel free to just take the code

[thomas.diesler]

Thanks Eric. I added your test here. The underlying issue is probably that the BundleWiring does not correctly expose capabilities from attached fragments. This is now tested (fails) here

public void testExportedPackageFromFragment() throws Exception {
    XBundle hostA = (XBundle) installBundle(getHostA());
    XBundle fragmentA = (XBundle) installBundle(getFragmentA());

    hostA.start();
    assertBundleState(Bundle.ACTIVE, hostA.getState());
    assertBundleState(Bundle.RESOLVED, fragmentA.getState());

    BundleWiring wiring = hostA.getBundleRevision().getWiring();
    List<BundleCapability> caps = wiring.getCapabilities(PACKAGE_NAMESPACE);
    assertEquals("One package capability", 1, caps.size());
    assertEquals("org.jboss.osgi.fragment", caps.get(0).getAttributes().get(PACKAGE_NAMESPACE));
}

Please note however that the expected exporter of the package is the host and not the fragment.

The related jira issue is

https://issues.jboss.org/browse/JBOSGI-571