Currently `javax.transaction`and `javax.transaction.xa` are imported from the JDK via the Stanbol framework fragment. This is potentially dangerous as the versions included in the JDK are incomplete. This can be easily checked by comparing the package summary of the packages in the Java6 javadoc  and the documentation of JSR 907: Java Transaction API (JTA) available at 
This is for an OSGI environment especially dangerous vor several reasons:
1. OSGI does not allow to import classes for the same package from different bundles
2. As `javax.transaction.*` is exported from the system bundle it uses version 0.0.0 and not the correct JSR 907 version 1.1.
3. javax.transaction is referenced by `javax.sql` that is also exported from the system bundle. So `javax.sql` will always bind to the `javax.transaction` package exported by the system bundle. That means that Bundles that require both the full JTA AND SQL will end up importing two versions from the `javax.transaction.*` (1) version 1.1 from a user provided bundle with the full JSR 907 specification (e.g. ) and indirectly 0.0.0 provided by the system bundle (indirectly via the `javax.sql` package. This will cause OSGI to report a Constraint violations because a bundle MUST NOT depend on two versions of the same package (such a setting is best described in  page 101ff.
A check with all modules present in the Stanbol Full Launcher showed that `javax.transaction` is only referenced by the Contenthub component. That means that we will need to add a Bundle for JTA 1.1 in the bundlelist for the Contenthub. I suggest to use the bundle provided by the JBoss community . All other options are not packaged as OSGI bundles and  does not come with any additional dependencies.