aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giuseppe Gerla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1251) Support jpa 2.0 and 2.1 with the same code base
Date Tue, 07 Oct 2014 13:01:33 GMT

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

Giuseppe Gerla commented on ARIES-1251:
---------------------------------------

Hi Christian
I solved my problem on JTA. Now I pass all tests of JPA 2.0 and I have only 2 error on JPA
2.1 tests.
Errors are due to the fact that EclipseLink wants a call to joinTransaction before calling
methods like flush. I saw that the call to JoinTransaction is inhibited in the class JTAEntityManagerHandler


if ("JoinTransaction" .equals (method.getName ())) {
             // This should be a no-op for a JTA entity manager 
             return null; 
         } 

How can I avoid this problem?

> Support jpa 2.0 and 2.1 with the same code base
> -----------------------------------------------
>
>                 Key: ARIES-1251
>                 URL: https://issues.apache.org/jira/browse/ARIES-1251
>             Project: Aries
>          Issue Type: Improvement
>          Components: JPA
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>
> We currently have two separate code bases for jpa 2.0 and 2.1 support. This is very difficult
to manage when we do source code changes.
> So I will try to create one code that supports both jpa 2.0 and 2.1 by using Dynamic
Proxies where we implement EntityManager or EntityManagerFactory. 



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

Mime
View raw message