OSGi Release 7 Errata

Core

3.9.5
The system bundle can export java.* packages in Release 7. The text is updated to remove the reference to the system bundle exporting non-java.* packages.

3.14
Bullet 3 is changed to remove the sentence: “The bundle-version attributes and bundle-symbolic-name attributes will reflect the host bundle.”

10.8.4
The text “If the meta-annotated annotation declares an element of the same name as an element in this annotation, the element is considered to override the element in this annotation.” is removed from the specification of the Capability annotation.

10.8.10
The text “If the meta-annotated annotation declares an element of the same name as an element in this annotation, the element is considered to override the element in this annotation.” is removed from the specification of the Requirement annotation.

Compendium

101.12.6
The arguments to the LoggerFactory getLogger methods must not be in null.

105.8
The version of the Meta Type Resource XML Schema is 1.4.0 and the namespace is http://www.osgi.org/xmlns/metatype/v1.4.0. The specification incorrectly included the 1.3.0 schema.

150.3.1
Table 150.1 is updated to correct the spelling of :configurator:symbolic-name. It incorrectly stated the spelling as :configurator:symbolicname.

151.4.1.1
The discussion of clashing resource mappings is updated to clarify the expected behaviour when multiple whiteboard resources provide resource methods which map to the same URI. The previous text failed to define how the ranking of these services would interact with the existing JAX-RS resource selection algorithm.

The updated text requires that higher ranked services take precedence over lower ranked services, but that equally ranked services fall back to the default JAX-RS resource method selection algorithm. It remains the case that static resources in a whiteboard application behave as if they have a ranking less than that of all whiteboard services.

150.11
The discussion of the osgi.identity capability is updated to correct the spelling of :configurator:symbolic-name. It incorrectly stated the spelling as :configurator:symbolicname.