This version of DataNucleus AccessPlatform builds on the 2.x releases, adding on more features
around the currently supported datastores, improving their completeness, and providing initial
support for data federation. As this is a major release cycle many internal APIs are changed from 2.x.
All releases are checked regularly against the JDO/JPA TCKs, meaning that DataNucleus is always
stable 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 3.0.3 to 3.0.4 will require the following changes.
Move java.awt geometric type support into
Migrating from AccessPlatform 3.0.2 to 3.0.3 will require no changes.
Migrating from AccessPlatform 3.0.1 to 3.0.2 will require the following changes.
HBase : Default behaviour was to use Java serialisation to get the bytes of the PK
of objects. This is changed to now use HBase Bytes.toBytes resulting in cleaner PK ROW ID. To get
the old behaviour set the persistence property
HBase : default behaviour used to be to persist primitive wrapper fields as serialized.
They are now persisted as serialised if specified in metadata, otherwise using HBase Bytes handler
Migrating from AccessPlatform 3.0.0 M6 to 3.0.0 RELEASE will require no changes.
Migrating from AccessPlatform 3.0.0 M5 to 3.0.0 M6 will require the following changes.
The plugin attribute "override" utilised by "java_type", "store_mapping" and "rdbms_mapping" is
now removed, and users should make use of the attribute "priority" (specify a number and the higher
the number the higher the priority that plugin extension gets.
JPA usage now defaults to use "datanucleus.RetainValues". This means that when an object
leaves a transaction it will not move to HOLLOW state, but instead to PERSISTENT NONTRANSACTIONAL
and has its field values intact.
If using an identity string translator, note that this is now a IdentityStringTranslator and the
persistence property is now "datanucleus.identityStringTranslatorType"
Migrating from AccessPlatform 3.0.0 M4 to 3.0.0 M5 should require no changes.
Migrating from AccessPlatform 3.0.0 M3 to 3.0.0 M4 will require the following changes.
Maven2 plugin option "outputFile" is renamed to "ddlFile" for consistency with all docs/tools
Migrating from AccessPlatform 3.0.0 M2 to 3.0.0 M3 will require the following changes.
Anyone using "memcache" cache provider should rename it to "spymemcached". This renaming
is to clarify which implementation of "memcached" is actually being used. Similarly the
persistence properties are now spelt "memcached" instead of "memcache". Also the former property
is dropped and users should use
HBase : previously all primitives were stored serialised. Set the metadata 'serialized'
flag on the field/property to continue doing that.
Queries are no longer run in a separate thread (which was the previous way of supporting
query cancellation, now reworked for RDBMS to use SQL error codes).
Persistence properties for schema validation
now default to false
Migrating from AccessPlatform 3.0.0 M1 to 3.0.0 M2 will require the following changes.
The connection password decryption interface has been repackaged/renamed to
so if you were
providing your own decryption of passwords then rebuild to this
If using your own DataNucleus plugins, make sure you specify the persistence property
since the default is now to just
use official DataNucleus plugins.
The identifier naming strategy
has been renamed to
to make it clearer that it was used as the default for DataNucleus v1.x but no longer
Migrating from AccessPlatform 2.2.x to 3.0.0 M1 will require the following changes.
JDO API has been moved into its own plugin "datanucleus-api-jdo" and you will need this
if using the JDO API. JDO classes have been repackaged to
and this is of particular importance for your PMF class
"datanucleus-jpa" jar has been repackaged as "datanucleus-api-jpa" and the classes within
repackaged to "org.datanucleus.api.jpa". In particular your JPA persistence provider
class should reference this new package name
"datanucleus-rest" jar has been repackaged as "datanucleus-api-rest".
SchemaTool (and its Ant task) has been moved in package to
HBase : generation of "family name" has changed when previously specifying a column name
without a colon; previously used that as family name and qualifier name, but now uses
the table name as the family name in that situation.
HBase : previously all relationships were stored serialised. Set the metadata 'serialized'
flag on the field/property to continue doing that.
Migrating from AccessPlatform 2.2.0 RELEASE to 2.2.1 will require the following changes.
JDO 3.1 changes the return type of JDOQL "AVG" to be double or BigDecimal depending
on the type being averaged (previously just returned the same type as the averaged type).
Migrating from AccessPlatform 2.2.0 M3 to 2.2.0 RELEASE will require the following changes.
is no longer provided/needed, and is included within
. In addition, if using JDK1.6 you can use a builtin DBCP connection pool.
You still need to include the relevant connection pool (e.g DBCP) in your CLASSPATH if using
If you experience different behaviour with delete of objects with Excel or ODF, this is
because they now support cascade-delete
Major changes have been made to the use of the L2 cache (so that fields are used from there
rather than from the datastore wherever possible) and also to Managed Relations. Please report
Migrating from AccessPlatform 2.2.0 M2 to 2.2.0 M3 will require the following changes.
was removed since no longer
needed - the default attach handler copes with all situations.
Much improved support for collections/arrays/maps containing nulls is now present
to better match the Java spec for types. If any problems come up, make use of the
"allow-nulls" extension metadata
JPA Criteria query annotation processor is now in its own plugin jar known as
JDO Typesafe query annotation processor is now in its own plugin jar known as
Migrating from AccessPlatform 2.2.0 M1 to 2.2.0 M2 will require the following changes.
NucleusJDOHelper methods for getting dirty/loaded fields have been improved.
Check the docs for the new method names.
JDO3.1 sequence changes allow specification of "allocationSize" and "initialValue".
These default to 50 and 1 respectively. Set them for your sequences as required.
The persistence properties now become only fallback values
Migrating from AccessPlatform 2.1.x to 2.2.0 M1 will require the following changes.
Legacy JDOQL implementation for RDBMS is now dropped. Use AccessPlatform 2.1 if you
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.