Excel (OOXML) Documents

DataNucleus supports persisting/retrieving objects to/from OOXML documents (using the datanucleus-excel plugin). It makes use of the Apache POI project. If you wish to contribute to this plugin either by contributing or by sponsoring particular functionality please contact us via the DataNucleus Forum.

Datastore Connection

DataNucleus supports file-based OOXML documents currently.

The following persistence properties will connect to a local file on your local machine


replacing "myfile.xlsx" with your filename, which can be absolute or relative.

So you create your PersistenceManagerFactory or EntityManagerFactory with these properties. Thereafter you have the full power of the JDO or JPA APIs at your disposal, for your Excel datastore.


Access Platform allows you to query the objects in the datastore using the following

  • JDOQL - language based around the objects that are persisted and using Java-type syntax
  • JPQL - language based around the objects that are persisted and using SQL-like syntax

Mapping : OOXML Document Mapping

Excel (OOXML) datastore support assumes that objects of a class are persisted to a particular "sheet" of a spreadsheet. Similarly a field of a class is persisted to a particular "column" index of that "sheet". This provides the basis for Excel persistence. When persisting a Java object to an Excel spreadsheet clearly the user would like some control over what worksheet a class is persisted to, and to what column number a field is persisted. DataNucleus provides extension metadata tags to allow this control. Here's an example, using JDO XML metadata

    <package name="mydomain">
        <class name="Person" detachable="true" table="People">
            <field name="personNum">
                <column position="0"/>
            <field name="firstName">
                <column position="1"/>
            <field name="lastName">
                <column position="2"/>

Note the following metadata usages (all are optional)

  • The table defines the name of the worksheet to use for that class.
  • The column defines the column name to use for the field.
  • The position of the column defines the position in the worksheet of this column. This is new in JDO3.1 and is optional (the default is to put the fields in alphabetical order).

Here's the same example using JDO Annotations

public class Person
    long personNum;

    String firstName;

    String lastName;

Here's the same example using JPA Annotations (with DataNucleus @Extension/@Extensions annotations)

public class Person
    long personNum;

    String firstName;

    String lastName;


Obviously a spreadsheet cannot store related objects directly since each object is a row of a particular spreadsheet table. DataNucleus gets around this by storing the String-form of the identity of the related object in the relation cell. We also support using @Embedded to embed an object within the worksheet of another object.