incubator-isis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <>
Subject [jira] [Commented] (ISIS-14) Add JDO 3.1 object store in order to support any datastore
Date Tue, 17 Jul 2012 08:43:34 GMT


Andy Jefferson commented on ISIS-14:

Hi Dan, just coincidence, going through all issues in Apache JIRA that mention "DataNucleus";
hadn't noticed you'd started on it :-) Only thing to add is that while DN 3.1 is imminent
(which implements JDO3.1 as well as all earlier versions), the JDO 3.1 API (provided by Apache
JDO) will likely take longer and you can safely build against JDO 3.0 API since very little
is changed API wise between v3.0 and v3.1 of the API. If you have any questions around getting
this implemented, mail me at {firstname} AT datanucleus DOT org. Thx
> Add JDO 3.1 object store in order to support any datastore
> ----------------------------------------------------------
>                 Key: ISIS-14
>                 URL:
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Matthew T. Adams
>            Assignee: Dan Haywood
>             Fix For: 0.3.0-incubating
> Given that JDO's charter is to be datastore-agnostic, a JDO object store should be high
on the list.  It supports both relational and non-relational databases, including object databases,
NoSQL data stores and **literally** anything else.
> By leveraging the plugins of DataNucleus, the Apache-licensed open source JDO reference
implementation, the following object stores below can be supported out of the box.
> RDBMS (all major vendors)
> DB4O
> Excel
> Neodatis
> HBase
> See for more info.
> Google's BigTable could also be supported thanks to their Google AppEngine for Java persistence
solution, which is a DataNucleus plugin, enabling Isis- & JDO-based apps to run on GAEJ.
> Note that DN also supports Joda & javax.time datetime types as well.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message