Grails

Add support for JDO

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Persistence
  • Labels:
    None

Description

Add support for JDO 2.0 and 1.0 implementations.

JDO 2.0, as of the time this issue was entered, has been finalized by the JCP, with JPOX, an open source JDO implementation, identified as the JDO 2.0 Reference Implementation.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Steven Devijver added a comment -

Grails tightly integrates with Hibernate 3. We've had to invest a lot of time and effort to create a custom configuration mechanism for Hibernate and we don't plan to repeat this for JDO since we feel this won't add new features to Grails.

We understand there may be political motivations to use JDO or any other persistence framework. However, Grails is not a framework that allows choice, it's a framework for high-productivity. If another persistence frameworks would add new features to Grails compared to Hibernate 3 we will consider switching. Until them we stick to Hibernate 3.

Show
Steven Devijver added a comment - Grails tightly integrates with Hibernate 3. We've had to invest a lot of time and effort to create a custom configuration mechanism for Hibernate and we don't plan to repeat this for JDO since we feel this won't add new features to Grails. We understand there may be political motivations to use JDO or any other persistence framework. However, Grails is not a framework that allows choice, it's a framework for high-productivity. If another persistence frameworks would add new features to Grails compared to Hibernate 3 we will consider switching. Until them we stick to Hibernate 3.
Hide
Permalink
Matthew Adams added a comment -

That's too bad. It seems short-sighted to me in today's persistence market to design something without regard to other persistence APIs, at least JDO 2.0 & EJB 3.0's JPA. There are plenty of organizations that not have existing investments in other persistence APIs and implementations, and Hibernate may not be a viable choice. Besides, there is so much overlap across the persistence APIs & implementations that it seems abstractable.

Show
Matthew Adams added a comment - That's too bad. It seems short-sighted to me in today's persistence market to design something without regard to other persistence APIs, at least JDO 2.0 & EJB 3.0's JPA. There are plenty of organizations that not have existing investments in other persistence APIs and implementations, and Hibernate may not be a viable choice. Besides, there is so much overlap across the persistence APIs & implementations that it seems abstractable.
Hide
Permalink
Jeff Brown added a comment -

Today, Grails does have support for EJB 3.0 mapping. See http://www.infoq.com/articles/grails-ejb-tutorial for a great tutorial.

Show
Jeff Brown added a comment - Today, Grails does have support for EJB 3.0 mapping. See http://www.infoq.com/articles/grails-ejb-tutorial for a great tutorial.
Hide
Permalink
Matthew Adams added a comment -

For the benefit of anyone tracking this issue, JDO is now supported on Google App Engine for Java:

http://blog.springsource.com/2009/05/14/grails-111-released-with-google-appengine-support/

Show
Matthew Adams added a comment - For the benefit of anyone tracking this issue, JDO is now supported on Google App Engine for Java: http://blog.springsource.com/2009/05/14/grails-111-released-with-google-appengine-support/

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.1#660-r161644) | Report a problem
Powered by a free Atlassian JIRA open source license for Grails project. Try JIRA - bug tracking software for your team.