[
https://issues.apache.org/jira/browse/ROL-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Johnson closed ROL-1891.
------------------------------
Resolution: Fixed
Author: snoopdave
Date: Sun Nov 14 21:17:06 2010
New Revision: 1035070
URL: http://svn.apache.org/viewvc?rev=1035070&view=rev
Log:
Fixes to allow Roller JUnit tests to run against EclipseLink JPA. Most changes
involved adding code to manage both ends of a one-to-many, or many-to-one
relationships. EclipseLink JPA is picky about this and I guess OpenJPA was not.
Left the EclipseLink stuff in the POMs for now, commented out. Might be nice
someday to have different Maven build profiles for the different options, so
testing against EclipseLink JPA, Hibernate JPA and OpenJPA can be automated.
> 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.
