Release4 / Errata
Search:

OSGi Service Platform Release 4 Errata

Version 4.1

3.14.2
Fragments During Runtime. Erroneously specified that fragments could become unresolved due to calling resolveBundles
6.1.4.29
Steps 4 and 7 are updated to reflect lazy activation.
  1. If this bundle's state is not STARTING or ACTIVE then this method returns immediately.
  1. If this bundle's state was ACTIVE prior to setting the state to STOPPING, the stop method of this bundle's BundleActivator, if one is specified, is called. If that method throws an exception, this method must continue to stop this bundle and a BundleException must be thrown after completion of the remaining steps.
6.1.14.3-5
The source of the PACKAGE_REFRESHED, STARTED and STARTLEVEL_CHANGED FrameworkEvent types is the System Bundle.
104.5.3
The following step was incorrectly added to the specification and has been removed.
  • A Configuration Event CM_UPDATED is send asynchronously out to all registered Configuration Listener services.
104.8
A Configuration Event CM_UPDATED in only sent when a Configuration is updated. No Configuration Event is sent when a Configuration is created.
112.10
In the XML Schema, the property type of Character is incorrectly listed at Char.
113.6.1
Table 113.23 contains a misspelling of EXCEPTION_CLASS. Also, the notes for EXCEPTION_CLASS and EXCEPTION_MESSAGE are reversed.
113.12.5
The code example has some minor bugs in it. EventConstants.EVENT_TOPIC should not be in the topics array and the key used for putting the topics array in the hashtable should be EventConstants.EVENT_TOPIC.
704.4.1
The Measurement compendium specification talks about a String constructor for the Measurement class. This constructor does not exist.

Version 4.0

The following errata from the original version of the R4 Core and Compendium specifications have been corrected in the Version 4.0.1 documents.

1.2
The bullet on signed bundles incorrectly refers to Package Admin. It should refer to Permission Admin.
3.2.1.8
The paragraph incorrectly refers to a Bundle-Location header. It should refer to the Bundle-Localization header.
3.3.1
Additional execution environment names have been defined for Java 2 SE 5.0 and Java SE 6.0. They are J2SE-1.5 and JavaSE-1.6, respectively.
3.5.5
The description of the exclude directive incorrectly refers to resources. Only classes may be excluded or included.
3.16.2
The section should state that a Framework that supports Require-Bundle and/or fragments must also support Bundle Permission.
4.3.12
The framework may resolve a bundle during the execution of Bundle.findEntries.
4.8.3
The framework must not call the constructor of a BundleActivator object from within a doPrivileged region.
9.6
In the example code, the fields EMPTY_CS and EMPTY_PS should be arrays 
ConditionInfo[] EMPTY_CS = new ConditionInfo[0];
PermissionInfo[] EMPTY_PS = new PermissionInfo[0];
104.4.2
The format of a property name should be symbolic-name. It is incorrectly stated as "must be". While it is recommended that property names conform to symbolic-name, they can be any valid String.
104.14
A property name is now recommended to conform to symbolic-name. It is incorrectly stated to be defined as unique-name.
105.1.2
Package in class diagram must be org.osgi.service.metatype, not org.osgi.service.metatyping
105.5
Example printing of metatypes contains syntax errors
105.6.2
Example MetaData element twice and incorrect. Should be merged and use default namespace
105.8
The content attribute of the Attribute element is not required and is changed to be optional. The bundle attribute of the Designate element is not required and is changed to be optional. A Value element is added as a child of the Attribute element to allow multiple values for an Attribute. 
<complexType name="Attribute">
	<sequence>
		<element name="Value" type="string" minOccurs="0"
			maxOccurs="unbounded" />
	</sequence>
	<attribute name="adref" type="string" use="required" />
	<attribute name="content" type="string" use="optional" />
</complexType>
112.2.3
The component description in the example code does not properly define the event.topics property so that the value is a String array as required by the Event Admin specification. The property element should be:
<property name="event.topics">some/topic</property>
112.4.3, 112.10
The component elemement of the component description shows the subelements occuring in the following order: implementation, properties/property, service, reference. This ordering is also specified in the XML schema. SCR must not require component descriptions to specify the elements in the order listed above and as required by the XML schema. SCR must allow other orderings since arbitrary orderings of these elements do not affect the meaning of the component description. Only the relative ordering of property and properties element have meaning.
113.4
Example uses EVENT_TOPICS instead of EVENT_TOPIC. The example with AcmeWatchDog must extend BundleActivator, not Activator
113.5
Timer example should have Calendar.MINUTE and Calendar.HOUR (they are now spelled with an extra S)
113.11.4.5
Event Handlers which do not have a value for the event.topics property must not receive events.
113.11.4.8
The constant name EXCEPTION_CLASS was released with an incorrect spelling. This error will be corrected in the next release and the incorrectly spelled constant name EXECPTION_CLASS will be deprecated.
999.4.3
The getLocalizedMessage method is incorrectly listed under java.lang.Thread. It should be listed under java.lang.Throwable.

Note: The errata for the OSGi API is made available under the OSGi Specification License, Version 1.0.