FYI...
Craig
Begin forwarded message:
From: "Michael Dick (JIRA)" <j...@apache.org>
Date: March 31, 2011 2:45:05 PM PDT
To: d...@openjpa.apache.org
Subject: [jira] [Commented] (OPENJPA-1744) Support JDO
Reply-To: d...@openjpa.apache.org
[ https://issues.apache.org/jira/browse/OPENJPA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014225
#comment-13014225 ]
Michael Dick commented on OPENJPA-1744:
---------------------------------------
Most of the nonrelational support is still in place - a rudimentary
xml store was part of the initial code drop and is (afaik) still
usable.
Implementing a different spec on top of the OpenJPA kernel would be
a significant undertaking. Is there anything specific to JDO that
makes it more (or less) usable with non relational stores? I'm
looking for pros and cons of adding JDO over implementing a hadoop /
big table store that uses JPA interfaces?
Support JDO
-----------
Key: OPENJPA-1744
URL: https://issues.apache.org/jira/browse/
OPENJPA-1744
Project: OpenJPA
Issue Type: Improvement
Reporter: Matthew T. Adams
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
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@oracle.com
P.S. A good JDO? O, Gasp!