Colm O hEigeartaigh closed CXF-6595.

> CXF Karaf feature file: set dependency = true in the jta bundle for CXF
> -----------------------------------------------------------------------
>                 Key: CXF-6595
>                 URL: https://issues.apache.org/jira/browse/CXF-6595
>             Project: CXF
>          Issue Type: Bug
>          Components: OSGi
>    Affects Versions: 3.1.2
>         Environment: Karaf 4.0.1
>            Reporter: Jochen Walz
>            Assignee: Christian Schneider
>             Fix For: 3.1.4
> Currently, geronimo-jta_1.1_spec is installed in any case when installing the 
> CXF feature in Karaf. This causes a conflict if another version of the 
> transaction api (1.2.0) has already been installed, e.g. with the Karaf 
> eclipselink feature.
> Adding some more details from mailing list:
> When installing the new eclipselink feature (version 2.6.0) together with CXF
> 3.1.2, there seems to be a conflict with two versions of the
> transaction-api: eclipselink brings version 1.2.0 with
> javax.transaction-api, CXF brings 1.1.0 with geronimo-jta_1.1_spec. When
> both are installed, Aries Transaction Blueprint doesn't get the
> javax.transaction.TransactionManager objectClass, and therefore doesn't
> provide the transaction namespace.
> When I remove geronimo-jta_1.1_spec from the cxf-transports-jms of CXF,
> Aries Transaction Blueprint works. I haven't checked whether CXF functions
> are still available, but at least all bundles are activated. And a
> persistence unit at least reaches the failure point described  here
> <http://karaf.922171.n3.nabble.com/Bundle-is-waiting-for-namespace-handlers-http-aries-apache-org-xmlns-jpa-v1-0-0-td4042275.html>
> (by the way: I would also be interested in a solution for that one).
> My question: is there a better way to reach this? Or would this a Jira for
> CXF to update the cxf-transports-jms feature to use the newer transaction
> API?

This message was sent by Atlassian JIRA

Reply via email to