You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@roller.apache.org by "David Johnson (JIRA)" <ji...@apache.org> on 2010/11/14 16:57:13 UTC

[jira] Updated: (ROL-1891) JUnit tests fail when run against EclipseLink JPA

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

David Johnson updated ROL-1891:
-------------------------------

    Description: 
If you replace OpenJPA v2 with EclipseLink JPA v2 in the build scripts, you will find that many of the JUnit tests fail. If the tests can't run against EclipseLink JPA, then there is not much chance that Roller will run against EclipseLink JPA (the JPA implementation in both GlassFish and WebLogic). 

We shouldn't switch Roller to EclipseLink JPA, but we should ensure that the Roller JUnit tests will work with EclipseLink JPA so that those who wish to run Roller with their app server's "native" JPA implementation have some hope.


 

  was:
If you replace OpenJPA v2 with EclipseLink JPA v2 in the build scripts, you will find that many of the JUnit tests fail. If the tests can't run against EclipseLink JPA, then there is not much chance that Roller will run against EclipseLink JPA (the JPA implementation in both GlassFish and WebLogic). 

We shouldn't switch Roller to EclipseLink JPA, but we should ensure that the Roller JUnit tests will work with EclipseLink JPA so that those who wish to run Roller with their app server's "native" JPA implementation can do so.


 


> JUnit tests fail when run against EclipseLink JPA
> -------------------------------------------------
>
>                 Key: ROL-1891
>                 URL: https://issues.apache.org/jira/browse/ROL-1891
>             Project: Roller
>          Issue Type: Improvement
>          Components: Database Access & Data Model
>    Affects Versions: 5.0
>            Reporter: David Johnson
>            Assignee: David Johnson
>             Fix For: 5.0
>
>
> If you replace OpenJPA v2 with EclipseLink JPA v2 in the build scripts, you will find that many of the JUnit tests fail. If the tests can't run against EclipseLink JPA, then there is not much chance that Roller will run against EclipseLink JPA (the JPA implementation in both GlassFish and WebLogic). 
> We shouldn't switch Roller to EclipseLink JPA, but we should ensure that the Roller JUnit tests will work with EclipseLink JPA so that those who wish to run Roller with their app server's "native" JPA implementation have some hope.
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.