DataNucleus AccessPlatform 2.1 builds on the 2.0 release, adding on more features around
the currently supported datastores and supporting new datastores.
All releases are checked regularly against the JDO/JPA TCKs, meaning that DataNucleus has
reached a level of stability in terms of functionality.
Occasionally, due to unknown bugs, or due to new functionality being introduced we need to
change some aspects of DataNucleus. As a result sometimes users will have to make some
changes to move between versions of DataNucleus. We aim to keep this to a minimum.
Migrating from AccessPlatform 2.1.2 to 2.1.3 will require the following changes.
is now removed, and
the default handling should work fine
Migrating from AccessPlatform 2.1.1 to 2.1.2 will require the following changes.
The metadata extension
that is used to specify a column position (in table)
was previously required under "field" for Excel/ODF plugins.
It should be under "column" now
Migrating from AccessPlatform 2.1.0 Release to 2.1.1 will require the following changes.
Default allocation size for
value strategies have
been changed for JDO usage to 10 and 10 respectively (from 5 and 1). You can configure
the global defaults via persistence properties
Migrating from AccessPlatform 2.1.0 M3 to 2.1.0 Release will require the following changes.
Move to using JDO3 jar instead of JDO 2.3 "ec"
Dropped support for class-level metadata extension "cacheable"; use standardised
attribute (or annotation) instead.
Migrating from AccessPlatform 2.1.0 M2 to 2.1.0 M3 will require no changes.
Migrating from AccessPlatform 2.1.0 M1 to 2.1.0 M2 will require the following changes.
JPQL "CASE" statements are now supported
JPA2 static metamodel is now supported, and so can be used with criteria queries
alongside the string-based field specification method
Runtime enhancement is now turned off by default even when you use JDK1.6+ and have
the enhancer/core jars in the CLASSPATH. Specify the compiler argument
to enable it (see docs)
Migrating from AccessPlatform 2.0.x to 2.1.0 M1 will require the following changes.
The JDOQL implementation used for RDBMS is now the rewritten "generic" implementation.
To use the old implementation, set the JDOQL implementation as "JDOQL-Legacy"
Use of JPA should be run against the JPA2 "final" jar (or its Apache Geronimo specs equivalent)
Heavy refactoring has been done internally so if relying on DataNucleus APIs you
should check against SVN for changes. In particular, plugins should be using ObjectProvider
instead of StateManager, and ExecutionContext in place of ObjectManager.