The main problem with the implementation of StAX API is that it looks for the StAX service provider (For example StAX Reference Implementation and Woodstox) in thread's context class loader which obviously is not suitable for an OSGi-based application. The provided API looks for the StAX service provider in the OSGi Environment even if provider's packages are not imported by the API bundle.

OSGi Compatible StAX API: org.dynamicjava.stax-api-1.0.jar

OSGi Compatible StAX API Source Code: org.dynamicjava.stax-api-1.0-src.zip

Original API's Source Code was taken from: http://stax.codehaus.org/

Test Application

The archive stax-api-test.zip contains an OSGi-based test application which has a StAX Consumer Bundle that uses classes from the StAX API. Alongside the StAX API bundle provided by DynamicJava.org there are the StAX bundle provided by Geronimo project and the StAX bundle provided with JCP 173 specification. The aim of this application not only to highlight the difference in the behavior between these different versions of the StAX API when run in an OSGi Environment but also to prove that the StAX API provided by DynamicJava.org is runnable with any StAX provider (StAX RI and Woodstox), with the OSGi Frameworks Felix, Equinox and Knopflerfish and in Java Environments JRE and JDK versions 1.5 and 1.6 - unlike other versions of the StAX API.