openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Nine (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-1744) Support JDO
Date Thu, 31 Mar 2011 22:32:05 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014248#comment-13014248
] 

Todd Nine commented on OPENJPA-1744:
------------------------------------

I've built the Cassandra JDO plugin on github.  I'm migrating from Datanucleus JDO to using
Open JPA and re-creating the framework.  To me JDO vs JPA is simply seem to be a matter of
preference.  The JPA spec cannot be fully supported using column based storage mechanisms.
 However most of the JDO spec in relation to querying is not supported either.  As a developer
of a plugin who as done both spec implementations in Cassandra, I think it simply is a preference.
 If the user is aware of the unsupported features in JPA and avoids them, I see no reason
to add additional complication to Open JPA.  The current framework is one of the most elegant
for building a custom storage provider in JPA.  I think adding JDO will make integration for
new providers more difficult.

> Support JDO
> -----------
>
>                 Key: OPENJPA-1744
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1744
>             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: http://www.atlassian.com/software/jira

Mime
View raw message