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

["Mark Struberg (JIRA)" <ji...@apache.org>]

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

Mark Struberg commented on OPENJPA-2607:
----------------------------------------

Christian, it sounds reasonable that OpenJPA will also work with JTA-1.2. So from this pov we could easily update to "[1.1.0,1.3)".
I would _not_ update to ,2) as I have no idea if the next version of JTA will be 1.3 or 2.0. Would need to talk to my EG mates.

One other question: what happens with a container which provides both jta spec versions per osgi? Is such a thing possible? Or is it a containers problem to solve this dependency problem (adding the 'right' of the 2 jars to the classloader)?

> 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)