You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2015/10/02 07:48:26 UTC

[jira] [Commented] (OPENJPA-2607) Import range for javax.transaction is to small

    [ https://issues.apache.org/jira/browse/OPENJPA-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940790#comment-14940790 ] 

Christian Schneider commented on OPENJPA-2607:
----------------------------------------------

We seem to have another issue with the limited import range for jta. The karaf jms feature requires jta 1.2. As soon as it is installed openjpa also breaks. So it would be really important to have the increased import range in the next bugfix versions.

> Import range for javax.transaction is to small
> ----------------------------------------------
>
>                 Key: OPENJPA-2607
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2607
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: osgi
>    Affects Versions: 2.2.2, 2.3.0, 2.4.0
>            Reporter: Christian Schneider
>             Fix For: 2.2.3, 2.3.1, 2.4.1
>
>
> Currently the import for javax.transaction looks like this:
> javax.transaction.*;version="[1.1.0,1.2)";resolution:=optional
> Unfortunately this makes openjpa incompatible with jta 1.2 which should be compatible for a consumer. As the Aries blueprint transaction support now uses jta 1.2 it does not work with openjpa.
> I just change the import range on trunk and tested using the aries itests. 
> It seems openjpa works fine with jta 1.2 if the import range is corrected like below:
> javax.transaction.*;version="[1.1.0,2)";resolution:=optional
> I only tested with trunk (2.4.1-SNAPSHOT) but the increased range should work for 2.3.x and 2.2.x too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)