Discussions

News: DataNucleus Access Platform 1.1.0 released

  1. DataNucleus Access Platform 1.1.0 released (2 messages)

    DataNucleus Access Platform 1.1.0 has just been released. Access Platform provides access to a range of datastores for Java applications using JDO/JPA API's. It is fully compliant with JDO1, JDO2, JDO2.1, JDO2.2, JPA1, and provides preview features for JDO2.3 and JPA2. It currently supports persistence to RDBMS, db4o, LDAP, XML, Excel, NeoDatis ODB, JSON and OpenDocumentFormat (ODF). It additionally allows configuration of classes to be persisted using JDO annotations/XML/API or JPA annotations/XML providing access to both JDO and JPA persistence APIs regardless of which configuration method was chosen, offering a level of flexibility not seen in other persistence tools. Querying of the supported datastores can be performed using JDOQL, JPQL or SQL (dependent on the datastore). By making use of standardised APIs, the process of swapping persistence from one datastore to another is a simple URL change when specifying the datastore. AccessPlatform is made up of a series of OSGi compliant jars, and can be utilised in J2SE, J2EE, or OSGi container environments. By using OSGi together with eclipse extension-points, DataNucleus is highly extensible so if you wanted to provide support for your own datastore then this would be a relatively simple procedure. DataNucleus Access Platform is licensed under the flexible Apache 2 license. DataNucleus Access Platform 1.1 provides the following over and above what DataNucleus 1.0 (originally JPOX) provides :-
    • Now requires JDK1.5+
    • Support for in-memory evaluation of JDOQL/JPQL subqueries
    • Support for JDO2 "PersistenceManager proxy"
    • Support for JDO2.3 Metadata API (for those that don't like XML *or* annotations)
    • Support for JDO2.3 Enhancer API
    • Support for JDO2.3 query timeout/cancel API
    • Support for JDO2.2 transaction isolation control
    • JPA2 preview support for datastore cache, @OrderColumn, standardised properties, and various new query methods
    • RDBMS : rewrite of locate, fetch and some select SQL using a new SQL API
    • RDBMS : start of an alternative JDOQL implementation using a new SQL API
    • RDBMS : Support for persistence of interface fields into a single column
    • ODF : Support for persistence/querying to OpenDocument format spreadsheets
    • XML : Added support for 1-1, 1-N, M-N relations
    • XML : Added many configurability improvements
    • LDAP : Support for various new mapping configurations.
    • LDAP : Support for native querying
    • Dropped support for BCEL enhancer, now focussing attention on the ASM variant
    • Many improvements to the L2 caching process
    • Some fixes for multithreaded usage
    Documentation is available to view online or PDF. It is available to download. Limited free support for Access Platform is provided by way of our forum. Commercial support and consulting is also provided. Thanks to NightLabs for their continued support and hosting. Thanks also to SourceForge for the provision of source code facilities used by DataNucleus. Finally, thanks to everyone who has helped in the development of DataNucleus Access Platform 1.1 over the last 5 months.

    Threaded Messages (2)

  2. Congrats![ Go to top ]

    Congrats Erik & Andy!! It's good to see how you guys show by implementation how cool and alive the JDO spec really is, and how it goes (light years) beyond that JPA thing. ;-) We use it for production and it allows us 1 component for all our persistence. We used to need 3 of them (one to dig up people from LDAP, the biggest buck for the RDMBS domain model interactions, and tEe 3rd one to interact with XML for e.g. our webservices). Keep up the good work and thanks for all the effort. -Wolf
  3. Re: Congrats![ Go to top ]

    Congrats Erik & Andy!!
    It's good to see how you guys show by implementation how cool and alive the JDO spec really is, and how it goes (light years) beyond that JPA thing. ;-)

    We use it for production and it allows us 1 component for all our persistence.
    We used to need 3 of them (one to dig up people from LDAP, the biggest buck for the RDMBS domain model interactions, and tEe 3rd one to interact with XML for e.g. our webservices).
    Keep up the good work and thanks for all the effort.

    -Wolf
    Thanks Wolf. Let's not forget the lead responsible to the recent major improvements in the LDAP support: Stefan Seelmann.