Spring Roo 1.0.0, EclipseLink 2.0.0 and JPA2 incompatible

Recently Spring Roo 1.0.0 was released. However for those interested in using Roo with EclipseLink (in other words for those with a fervent disdain of Hibernate) please note that this is not yet supported. The related online discussion is on the forum and there is an open JIRA for integrating it which you can vote on and watch. Apparently EclipseLink 2.0.0 has a dependency on JPA2 API which is causing issues. It’s a real shame that EclipseLink isn’t supported yet as it would have been useful on one of our projects going forward but this integration can always be done by hand.

2 thoughts on “Spring Roo 1.0.0, EclipseLink 2.0.0 and JPA2 incompatible”

  1. As the link to the forum discussion shows, we’re actively working on this. Concurrent to the Roo 1.0.0 release preparations we had a team member working on EclipseLink 2.0.0 interop testing. We had hoped to include it in Roo 1.0.0, but a few little issues were discovered too late in the cycle. Rest assured EclipseLink 2.0.0 will be forthcoming very shortly. In the meantime both OpenJPA and Hibernate work fully with Roo and you can switch from one JPA provider to another just by entering the “persistence setup” command in the Roo shell. You can execute this command as many times as you like, so you can start a Roo project right now with say OpenJPA or Hibernate and then switch to EclipseLink 2.0.x in just a few seconds once the Roo support is finalised. We fully wish to support all major JPA providers and EclipseLink is a clear priority.

    Ben Alex
    Project Lead, Spring Roo

Leave a Reply