Mike Keith wrote:Hi Josh,
They ship EclipseLink as the JPA 2.0 implementation.
Tim Holloway wrote:Actually, I believe that Roo can generate Maven projects. And I once ran into a JPA issue that was so thorny that the only quick cure was to switch implementations. With Maven, I changed 2 dependencies, did some minor edits on persistence.xml and was running on the new implementation in under half an hour.
Mike Keith wrote:Hi,
My last sentence was out of place. It should have been said earlier in the paragraph since what I was referring to Spring, not Roo, since Spring ships with EclipseLink. It is their means of providing JPA 2 because no other provider is JPA 2 compliant right now. It seems I need an editor more than I thought...
Yes, the Roo syntax is when you set up the persistence part:
persistence setup --provider <provider>
My main point was that Roo is all about JPA and shows the JPA direction of Spring. To my knowledge it (Roo) doesn't even support specific proprietary persistence product APIs.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton