You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2014/07/14 14:50:05 UTC

[jira] [Resolved] (ARIES-1200) JPA PersistentBundleManager does not work with OSGi 4.2

     [ https://issues.apache.org/jira/browse/ARIES-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved ARIES-1200.
-----------------------------------------

    Resolution: Fixed

> JPA PersistentBundleManager does not work with OSGi 4.2
> -------------------------------------------------------
>
>                 Key: ARIES-1200
>                 URL: https://issues.apache.org/jira/browse/ARIES-1200
>             Project: Aries
>          Issue Type: Bug
>          Components: JPA
>         Environment: Running JPA code with an OSGi 4.2 level
>            Reporter: Simon Gormley
>            Assignee: Jean-Baptiste Onofré
>         Attachments: JPANSMExption.diff
>
>
> JPA container code is compiled against OSGi 4.3, but is intended to work with 4.2
> If a JPA persistence unit is defined with a org.apache.aries.jpa.provider.version property that contains a version range, the PersistenceBundleManager.combineVersionRanges is driven, but fails due to the code trying to call an OSGi 4.3 specific method for compareTo (which has changed from compareTo(Object) to compareTo(Version)).
> One solution would be to catch the exception and attempt to use reflection to drive the Object version of the method. (Diff will be attached)



--
This message was sent by Atlassian JIRA
(v6.2#6252)