Hi everyone, For our storage evaluation, I've put together a JDO implementation in Nakamura [1] using DataNucleus. While JDO is storage agnostic (DataNucleus has quite a few storage drivers [2]), my current intention is that we would use it solely against a RDBMS. JDO/DataNucleus provides annotation-driven ORM capabilities, the ability to dynamically load and reload entity classes at runtime, and has OSGi class loader support in its design, which makes it a pretty attractive RDBMS API option in an OSGi container.
DataNucleus is licensed under ASL v2.0, and has been the reference-implementation for JDO (JSR-243) since version 2.2. [3] There appears to be some stigma, or lack of enthusiasm around JDO from its lack of adoption relative to JPA, and this could be a downside of using it. None-the-less, it seems that the specification continues to progress, as do the implementations (as scarce as the active implementations seem to be). I'm curious to hear the thoughts of others on JDO if any one has worked with it. Please check out the OAE community page [1] for more details about the implementation and source. [1] https://oae-community.sakaiproject.org/content#l=page1&p=l1iT8gqlie [2] http://www.datanucleus.org/products/accessplatform_3_0/datastore_features.html [3] http://db.apache.org/jdo/impls.html -- Cheers, Branden _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
