Persistent Fields or Properties

There are two distinct modes of persistence definition. The most common uses fields , whereas an alternative uses properties .

Persistent Fields

The most common form of persistence is where you have a field in a class and want to persist it to the datastore. With this mode of operation DataNucleus will persist the values stored in the fields into the datastore, and will set the values of the fields when extracting it from the datastore.

Requirement : you have a field in the class. This can be public, protected, private or package access, but cannot be static or final.

An example of how to define the persistence of a field is shown below

@PersistenceCapable
public class MyClass
{
    @Persistent
    Date birthday;
}

So, using annotations, we have marked this class as persistent, and the field also as persistent. Please note that in this particular case, Date is by default persistent so we could omit the @Persistent annotation (with non-default-persistent types we would definitely need the annotation). Using XML MetaData we would have done

<class name="MyClass">
    <field name="birthday" persistence-modifier="persistent"/>
</class>


Persistent Properties

A second mode of operation is where you have Java Bean-style getter/setter for a property . In this situation you want to persist the output from getXXX to the datastore, and use the setXXX to load up the value into the object when extracting it from the datastore.

Requirement : you have a property in the class with Java Bean getter/setter methods. These methods can be public, protected, private or package access, but cannot be static. The class must have BOTH getter AND setter methods.

An example of how to define the persistence of a property is shown below

@PersistenceCapable
public class MyClass
{
    @Persistent
    Date getBirthday()
    {
        ...
    }

    void setBirthday(Date date)
    {
        ...
    }
}

So, using annotations, we have marked this class as persistent, and the getter is marked as persistent. Using XML MetaData we would have done

<class name="MyClass">
    <property name="birthday" persistence-modifier="persistent"/>
</class>>


Overriding Superclass MetaData

If you are using XML MetaData you can also override the MetaData for fields/properties of superclasses. You do this by adding an entry for {class-name}.fieldName , like this

<class name="Hotel" detachable="true">
    ...
    <field name="HotelSuperclass.someField" default-fetch-group="false"/>

so we have changed the field "someField" specified in the persistent superclass "HotelSuperclass" to not be part of the DFG.