Problem Report Resolutions

Problem Report Resolutions for R3 Products

At this time, no PRRs have been noted for R3.

Problem Report Resolutions for R2 Products

  1. DEVIATION #129 NAME:cm.tc2
  2. DEVIATION #130 NAME:TestCaseDiv
  3. DEVIATION #131 NAME:framework.filter
  4. DEVIATION #138 NAME:rankTest method, SERVICE_RANKING property
 #129 cm.tc2 May fail with the following error:

  MESSAGE:
      - Error: configuration still not bound
      - Error: configuration still not bound
      - Error: configuration still not bound
      ....

This error is caused by a security issue that was closed after the spec was closed. The dictionary should not expose the bundle location. Passing this test will not reset compliance but will indicate that the framework is exposed to a security threat.

 #130 TestCaseDiv Effect in the result file:

  MESSAGE:
      - Exception in manifest headers org.osgi.framework.BundleException
      - NestedException java.io.CharConversionException
      ....
#131 framework.filter Effect in the result file:

  MESSAGE:
      - Testing type BigDecimal: No services.
      + Testing type BigDecimal: 1 services: { ServiceC 2.5 }

The R2 compliance test assumes a minimal environment but there is one test that uses BigDecimal and BigInteger classes. It is therefore advised to run the test on a J2SE execution environment. However, it is recognized that that vendors want to verify their implementations on J2ME environments, and claim appropriate compliance. It is therefore a valid deviation to fail the framework.filter test because BigInteger and BigDecimal are not available.

#138 rankTest method, SERVICE_RANKING property The rankTest method expects the getServiceReferences(…) method to return the ServiceReferences in a specific order, according to the SERVICE_RANKING property. However this is not requested anywhere in the spec. The Reference Implementation returns in random order so it is the test specification that is at fault and there is a 50% chance of passing it.