Created an issue to track the EclipseLink JPA part of this work: https://issues.apache.org/jira/browse/ROL-1891
- Dave On Sun, Nov 14, 2010 at 9:49 AM, Dave <[email protected]> wrote: > On Sun, Nov 14, 2010 at 9:42 AM, Matt Raible <[email protected]> wrote: >> On Nov 14, 2010, at 7:39 AM, Dave wrote: >>> So... what is the best way to ensure that Roller v5 can run on the >>> widest possible range of app severs? Here's a possible plan: >>> >>> 1) To ensure that Roller will run with other JPA implementations, run >>> the Roller JUnit tests against EclipseLinkJPA and Hibernate JPA and >>> fix any problems that arise. >>> 2) Ship two versions of Roller >>> 2.1) One for simple Servlet-only containers like Tomcat and Jetty. >>> 2.2) One for real Java EE 5 app servers that include JPA v2. >>> >>> Does that sound reasonable? Is step #1 really necessary? >> >> I get the feeling that we'd have to do #1 in order to do #2. It's not like >> you can just strip out the JPA JARs and expect everything to work, can you? >> If the JPA impls were as consistent as the servlet impls, I'd think >> different, but I don't think they are. > > That is the same feeling that I get. BTW, I have already tested > against EclipseLink JPA and had to make a bunch of small changes to > make the Roller JUnit tests running. I'll commit those changes later > today. Next, I plan to test against Hibernate JPA. > > - Dave >
