aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <>
Subject [jira] [Resolved] (ARIES-1234) Recreate Aries JPA 2.0 support
Date Tue, 30 Sep 2014 18:10:35 GMT


Christian Schneider resolved ARIES-1234.
    Resolution: Fixed
      Assignee: Christian Schneider  (was: Mark Nuttall)

Fixed this with the linked issue where I added support for jpa 2.0 and 2.1

> Recreate Aries JPA 2.0 support
> ------------------------------
>                 Key: ARIES-1234
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: JPA
>    Affects Versions: 0.4
>            Reporter: Mark Nuttall
>            Assignee: Christian Schneider
> Aries-1047 moved the JPA support up to JPA 2.1. However classes that implement the JPA
2.1 API cannot work against the JPA 2.0 API. 
> For example, javax.persistence.EntityManager has gained a number of new methods such
as createStoredProcedureQuery() which return an object of class javax.persistence.StoredProcedureQuery.
The class _does not exist_ in JPA 2.0. 
> A class that implements the 2.1 version of EntityManager can not be loaded under the
JPA 2.0 API. 
> org.apache.aries.jpa.container.impl.EntityManagerWrapper implements javax.persistence.EntityManager.
This means that it now has public API methods with class signatures that can not possibly
work in a JPA 2.0 environment. Attempts to do so yield errors of the form, 
> java.lang.ClassNotFoundException: javax.persistence.StoredProcedureQuery cannot be found
by org.apache.aries.jpa.container.context. 
> We need the JPA 2.0 code back. This will first be achieved by restoring the JPA container
code to /trunk/jpa20/... at the svn level before the commit that broke it,

> Most of the code remains common, but will require additional effort to refactor: this
can be done, if desired, under future JIRAs. 

This message was sent by Atlassian JIRA

View raw message