EclipseLink/UserGuide/JPA/Advanced JPA Development/NoSQL/Persistence Units
|Mailing List • Forums • IRC • mattermost|
|Open • Help Wanted • Bug Day|
NoSQL Persistence Units
NoSQL persistence units are configured the same as JPA persistence units. The
persistence.xml is used to define the persistence unit. NoSQL persistence units can be application managed, JTA managed, injected, or created through
Persistence the same as regular JPA persistence units. NoSQL persistence units do have some specific persistence unit properties that are required, and have some limitations.
NoSQL defines the following persistence unit properties:
"eclipselink.nosql.connection-spec"- this specifies an EISConnectionSpec class name that defines how to connect to the NoSQL data-source.
"eclipselink.nosql.connection-factory"- this specifies the JNDI name of a JCA ConnectionFactory, or a JCA ConnectionFactory class name that connects to the NoSQL data-source.
"eclipselink.nosql.property."- this prefix is used to pass driver specific properties to the NoSQL connection spec.
NoSQL persistence units have the following restrictions:
<non-jta-data-source>- these are not supported, as they refer to JDBC DataSources.
JTA- JTA managed persistence units are supported, but XA transactions may not be provided unless the NoSQL JCA resource adapter supports JTA.
"eclipselink.jdbc."- JDBC specific properties are not supported as NoSQL does not use JDBC.