openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <>
Subject [jira] [Commented] (OPENJPA-1744) Support JDO
Date Fri, 01 Apr 2011 23:51:05 GMT


Michael Dick commented on OPENJPA-1744:

@Matthew. I probably should have done more digging, and collision might not have been the
best term. There have been several issues that have cropped up where OpenJPA wasn't quite
honoring the JPA spec and the root caused appeared to be its JDO background. Since I'm not
well versed in JDO that might not always have been the case. 

The notion of which spec is a subset of the other probably depends on what you're interested
in. JDO notably does not have a criteria API (although there is a DSL available separately).
I'm sure there are examples of the reverse though. 

The main reason I think we're unlikely to add JDO support in the near term is to avoid doing
two things adequately and neither of them well. Despite our roots in JDO we're a JPA provider
first and foremost (how could we not be). If Oracle were to donate the Kodo code, that might
shift things, or if there were a lot of people volunteering to maintain a JDO front end. Right
now I think we have our hands full with JPA.

> Support JDO
> -----------
>                 Key: OPENJPA-1744
>                 URL:
>             Project: OpenJPA
>          Issue Type: Improvement
>            Reporter: Matthew T. Adams
>            Assignee: Michael Dick
> OpenJPA came from Kodo, which was a JDO implementation at the time the code was forked.
 This request is to bring compliance with the latest JDO specification back to the implementation
so that it can be used with nonrelational backends like Google BigTable, Hadoop, etc.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message