Description Glyn Normington 2011-03-31 06:22:02 EDT

The diagnostics issued to the event log contain uses violation diagnostics like this:

Unable to satisfy dependencies of bundle 'org.example.foo.xydata' at version '0.0.0': Cannot resolve: org.example.foo.xydata
    Resolver report:
        Uses violation: <Import-Package: org.example.foo.bar.datastore; version="0.0.0"> in bundle <org.example.foo.xydata_0.0.0[1301563814803]>
            Found conflicts:
                package        'org.example.foo.util.verify_1.0.0' in bundle 'org.example.foo.platform.util_0.0.0[1301563814806]' used by 'org.example.foo.bar.datastore_0.0.0' in bundle 'org.example.foo.bar.datastore_0.0.0[1301563814805]'
                conflicts with 'org.example.foo.util.verify_2.0.0' in bundle 'org.example.foo.framework_0.0.0[1301563814804]' imported by bundle 'org.example.foo.xydata_0.0.0[1301563814803]'

but when the corresponding state dump is viewed in the admin console OSGi state explorer, the unresolveable bundle shows the following diagnostics:

State resolver report for 'org.example.foo.xydata - 0.0.0'

Bundle Symbolic Name	org.example.foo.xydata
Bundle Version	0.0.0
Bundle ID	1301563814803
Hosts/Fragments	 NA
State	Unresolved
Cannot resolve: org.example.foo.xydata
    Unsatisfied leaf constraints:
        Bundle: org.example.foo.xydata_0.0.0 - Import-Package: org.example.foo.bar.datastore; version="0.0.0"
            Did you mean: 'org.eclipse.osgi.baseadaptor'?
        Bundle: org.example.foo.xydata_0.0.0 - Import-Package: org.example.foo.util.verify; version="[2.0.0,2.1.0)"
            Did you mean: 'org.eclipse.virgo.util.io'?

The OSGi state resolve should produce a uses constraint violation diagnostic as in the event log.

Steps to reproduce:
1. Place the attached bundles org.example.foo.bar.datastore.jar, org.example.foo.framework.jar, and		org.example.foo.platform.util.jar in repository/usr.
2. Deploy the attached bundle org.example.foo.xydata.jar e.g. by copying it to pickup.
3. Observe the uses constraint diagnostics in the event log.
4. Note the dump id in the event log, e.g. <ME0003I> Dump 'serviceability/dump/2011-03-31-10-30-868' generated.
5. In the admin console, navigate to the OSGi state explorer and choose the state dump observed in step 4 using the drop down.
6. Find the unresolved bundle org.example.foo.xydata and click on the "Unresolved" link.