Also, would it be possible to get it working by specify a version range, like:
Import-Package:javax.transaction;version=”[1.1,1.2)”
Lin
On Wed, Jun 10, 2009 at 4:06 PM, Lin Sunlinsun@gmail.com wrote:
Interesting prob... I wonder if you add the split-package (see
FWIW, Karaf solved the problem was explicitely removing the
javax.transaction package exported by the system bundle and deploying
the geronimo jta jar.
On Wed, Jun 10, 2009 at 19:58, Jarek Gaworjga...@gmail.com wrote:
Hey all,
I'm experimenting with JPA (OpenJPA specifically) in osgi
Btw, not sure how you deployed the tx manager (if you did so), but
there is an osgi bundle that i wrote to do that:
http://svn.apache.org/repos/asf/felix/trunk/transaction/
On Thu, Jun 11, 2009 at 17:03, Guillaume Nodetgno...@gmail.com wrote:
FWIW, Karaf solved the problem was explicitely
Hey all,
I'm experimenting with JPA (OpenJPA specifically) in osgi environment
and I ran into an interesting issue with the transaction API. The root
of the problem is that the JDK provides a *subset* of the
javax.transaction classes that the JTA specification defines. And that
creates problems
Interesting prob... I wonder if you add the split-package (see
http://www.aqute.biz/Code/Bnd) when you export the jta packages would
solve the prob for you. This is what I have been using but I only
tried Equinox so far.
Export-Package = \
First of all I think we should lean on felix to provide a 1.0 package
version for their tx classes.
Second without the split-bundle lin suggests wont' there be this
problem anyway since the system bundle will have used up the packages
and ours will be ignored?
thanks
david jencks
On Jun
