[ http://issues.apache.org/jira/browse/JDO-417?page=comments#action_12434529 ] Craig Russell commented on JDO-417: -----------------------------------
1. There are optional references to javax.transaction.Synchronization, that are only required if the user actually calls setSynchronization on the implementation instance that implements javax.jdo.Transaction. But it's not clear what value this adds to the bundle definition. 2. As far as I know, there is no reference anywhere in javax.jdo to javax.transaction.xa. What would be the purpose of including this reference? 3. Where did the Bundle-Version: 2.0.0 come from? There is no third digit in the official release. Wouldn't it be better to use Bundle-Version: 2.0? Thanks for the information. Once we figure out the right content, we can apply changes to both manifests (JDO1 and JDO2). > Make JDO jar an OSGI bundle > --------------------------- > > Key: JDO-417 > URL: http://issues.apache.org/jira/browse/JDO-417 > Project: JDO > Issue Type: Improvement > Components: api20 > Affects Versions: JDO 2 final > Reporter: Erik Bengtson > Priority: Minor > > Enable easy usage of JDO in OSGi containers by making the JDO jar an OSGI > bundle. The change is pretty simple, just add the below to the MANIFEST.MF > Manifest-Version: 1.0 > Bundle-ManifestVersion: 2 > Bundle-Name: Java Data Objects > Bundle-SymbolicName: javax.jdo > Bundle-Version: 2.0.0 > Export-Package: javax.jdo, > javax.jdo.datastore, > javax.jdo.identity, > javax.jdo.listener, > javax.jdo.spi > Bundle-Vendor: Apache -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
