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

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

Hi Mark,
sorry for the late response. Was on vacation. About the import range. is you 
set the upper bound to 2.0) it will exclude a 2.0.0 version but include 
everything 1.x. So as long as the next jta 1.x is compatible it should work.
If you want to be more converative then [1.1.0,1.3) will at least solve the 
current problem with jta 1.2.
Several versions of the spec could be installed at the same time. It would then 
only work though if the transaction manager implements every of the minor 
versions which is not the case today. 

The solution is to install the jta spec bundle with dependency=true. This makes 
sure that karaf will only install the highest version of jta all importing 
bundles are ok with. So this solves the above problem. 

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

Reply via email to