C Oracle Kodo Persistence Configuration Schema Reference

Function

Specifies a plugin string describing the kodo.kernel.BrokerFactory type to use, in this case abstract store.

Example

<abstract-store-broker-factory/>

Function

Defines configuration values for the Access Dictionary. For a complete description of each of the values that you can specify, see "Access Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

The default values for each of the configuration values are shown in the example below.

<access-dictionary>
    <char-type-name>CHAR</char-type-name>
    <outer-join-clause>LEFT OUTER JOIN</outer-join-clause>
    <binary-type-name>BINARY</binary-type-name>
    <clob-type-name>CLOB</clob-type-name>
    <supports-locking-with-distinct-clause>true</supports-locking-with-distinct-clause>
    <simulate-locking>false</simulate-locking>
    <system-tables>true</system-tables>
    <concatenate-function>({0}||{1})</concatenate-function>
    <substring-function-name>SUBSTR</substring-function-name>
    <supports-query-timeout>true</supports-query-timeout>
    <use-set-bytes-for-blobs>true</use-set-bytes-for-blobs>
    <max-constraint-name-length>18</max-constraint-name-length>
    <search-string-escape>\\</search-string-escape>
    <supports-cascade-update-action>true</supports-cascade-update-action>
    <string-length-function>CHAR_LENGTH({0})</string-length-function>
    <long-varbinary-type-name>LONGVARBINARY</long-varbinary-type-name>
    <supports-unique-constraints>true</supports-unique-constraints>
    <supports-restrict-delete-action>true</supports-restrict-delete-action>
    <trim-leading-function>LTRIM(LEADING '{1}' from {0})</trim-leading-function>
    <supports-default-delete-action>false</supports-default-delete-action>
    <next-sequence-query></next-sequence-query>
    <long-varchar-type-name>LONGVARCHAR</long-varchar-type-name>
    <cross-join-clause>CROSS JOIN</cross-join-clause>
    <max-embedded-clob-size>-1</max-embedded-clob-size>
    <date-type-name>DATE</date-type-name>
    <supports-schema-for-get-tables>true</supports-schema-for-get-tables>
    <supports-alter-table-with-drop-column>true</supports-alter-table-with-drop-column>
    <current-time-function>CURRENT_TIME</current-time-function>
    <requires-condition-for-cross-join>false</requires-condition-for-cross-join>
    <ref-type-name>REF</ref-type-name>
    <concatenate-delimiter>'OPENJPATOKEN'</concatenate-delimiter>
    <catalog-separator>.</catalog-separator>
    <supports-mod-operator>false</supports-mod-operator>
    <schema-case>upper</schema-case>
    <java-object-type-name>JAVA_OBJECT</java-object-type-name>
    <driver-vendor></driver-vendor>
    <supports-locking-with-multiple-tables>true</supports-locking-with-multiple-tables>
    <max-column-name-length>128</max-column-name-length>
    <double-type-name>DOUBLE</double-type-name>
    <use-get-string-for-clobs>false</use-get-string-for-clobs>
    <decimal-type-name>DECIMAL</decimal-type-name>
    <smallint-type-name>SMALLINT</smallint-type-name>
    <date-precision>1000000</date-precision>
    <supports-alter-table-with-add-column>true</supports-alter-table-with-add-column>
    <bit-type-name>BIT</bit-type-name>
    <supports-null-table-for-get-columns>true</supports-null-table-for-get-columns>
    <to-upper-case-function>UPPER({0}))</to-upper-case-function>
    <supports-select-end-index>false</supprots-select-end-index>
    <supports-auto-assign>false</supports-auto-assign>
    <store-large-numbers-as-strings>false</store-large-numbers-as-strings>
    <constraint-name-mode>before</constraint-name-mode>
    <allows-alias-in-bulk-clause>true</allows-alias-in-bulk-clause>
    <supports-select-for-update>true</supports-select-for-update>
    <distinct-count-column-separator></distinct-count-column-separator>
    <supports-subselect>true</supports-subselect>
    <time-type-name>TIME</time-type-name>
    <auto-assign-type-name></auto-assign-type-name>
    <use-get-object-for-blobs>false</use-get-object-for-blobs>
    <max-auto-assign-name-length>31</max-auto-assign-name-length>
    <validation-sql></validation-sql>
    <struct-type-name>STRUCT</struct-type-name>
    <varchar-type-name>VARCHAR</varchar-type-name>
    <range-position>0</range-position>
    <supports-restrict-update-action>true</supports-restrict-update-action>
    <auto-assign-clause></auto-assign-clause>
    <supports-multiple-nontransactional-result-sets>true</supports-multiple-nontransactional-result-sets>
    <bit-length-function>(OCTET_LENGTH({0}) * 8)</bit-length-function>
    <create-primary-keys>true</create-primary-keys>
    <null-type-name>NULL</null-type-name>
    <float-type-name>FLOAT</float-type-name>
    <use-get-bytes-for-blobs>true</use-get-bytes-for-blobs>
    <table-types>TABLE</table-types>
    <numeric-type-name>NUMERIC</numeric-type-name>
    <table-for-update-clause></table-for-update-clause>
    <integer-type-name>INTEGER<integer-type-name>
    <blob-type-name>BLOB</blob-type-name>
    <for-update-clause>FOR UPDATE</for-update-clause>
    <boolean-type-name>BOOLEAN</boolean-type-name>
    <use-get-best-row-identifier-for-primary-keys>false</use-get-best-row-identifier-for-primary-keys>
    <supports-foreign-keys>true</supports-foreign-keys>
    <drop-table-sql>DROP TABLE {0}</drop-table-sql>
    <use-set-string-for-clobs>false</use-set-string-for-clobs>
    <supports-locking-with-order-clause>false</supports-locking-with-order-clause>
    <platform>Generic</platform>
    <fixed-size-type-names></fixed-size-type-names>
    <store-chars-as-numbers>true</store-chars-as-numbers>
    <max-indexes-per-table>2147483647</max-indexes-per-table>
    <requires-cast-for-comparisons>false</requires-cast-for-comparisons>
    <supports-having>true</supports-having>
    <supports-locking-with-outer-join>true</supports-locking-with-outer-join>
    <supports-correlated-subselect>true</supports-correlated-subselect>
    <supports-null-table-for-get-imported-keys>false</supports-null-table-for-get-imported-keys>
    <bigint-type-name>BIGINT</bigint-type-name>
    <last-generated-key-query></last-generated-key-query>
    <reserved-words></reserved-words>
    <supports-null-update-action>true</supports-null-update-action>
    <use-schema-name>true</use-schema-name>
    <supports-deferred-constraints>true</supports-deferred-constraints>
    <real-type-name>REAL</real-type-name>
    <requires-alias-for-subselect>false</requires-alias-for-subselect>
    <supports-null-table-for-get-index-info>false</supports-null-table-for-get-index-info>
    <trim-trailing-function>TRIM(TRAILING '{1}' FROM {0}))</trim-trailing-function>
    <supports-locking-with-select-range>true</supports-locking-with-select-range>
    <storage-limitations-fatal>false</storage-limitations-fatal>
    <supports-locking-with-inner-join>true</supports-locking-with-inner-join>
    <current-timestamp-function>CURRENT_TIMESTAMP</current-timestamp-funct    <cast-function>CAST({0} AS {1})</cast-function>
    <other-type-name>OTHER</other-type-name>
    <max-index-name-length>128</max-index-name-length>
    <distinct-type-name>DISTINCT</distinct-type-name>
    <character-column-size>255</character-column-size>
    <varbinary-type-name>VARBINARY</varbinary-type-name>
    <max-table-name-length>128</max-table-name-length>
    <close-pool-sql></close-pool-sql>
    <current-date-function>CURRENT_DATE</current-date-function>
    <join-syntax>sql92</join-syntax>
    <max-embedded-blob-size>-1</max-embedded-blob-size>
    <trim-both-function>TRIM(BOTH '{1}' FROM {0})</trim-both-function>
    <supports-select-start-index>false</supports-select-start-index>
    <to-lower-case-function>LOWER({0})</to-lower-case-function>
    <array-type-name>ARRAY</array-type-name>
    <inner-join-clause>INNER JOIN</inner-join-clause>
    <supports-default-update-action>true</supports-default-update-action>
    <supports-schema-for-get-columns>true</supports-schema-for-get-columns>
    <tinyint-type-name>TINYINT</tinyint-type-name>
    <supports-null-table-for-get-primary-keys>false</supports-null-table-for-get-primary-keys>
    <system-schemas></system-schemas>
    <requires-cast-for-math-functions>false</requires-cast-for-math-functions>
    <supports-null-delete-action>true</supports-null-delete-action>
    <requires-auto-commit-for-meta-data>false</requires-auto-commit-for-meta-data>
    <timestamp-type-name>TIMESTAMP</timestamp-type-name>
    <initialization-sql></initialization-sql>
    <supports-cascade-delete-action>true</supports-cascade-delete-action>
    <supports-timestamp-nanos>true</supports-timestamp-nanos>
</access-dictionary>

Function

Flag that specifies whether to allow access to unloaded fields of detached objects. Set to false to throw an exception whenever an unloaded field is accessed. This option is only available when you use detached state managers.

Example

<access-unloaded>true</access-unloaded>

Function

Controls the action taken when the inverse manager detects an inconsistent bidirectional relation. Valid options include:

• warn—Log a warning.

• exception—Throw an exception.

Example

<action>warn</action>

Function

Specifies a semicolon separated list of IP addresses to which notifications should be sent.

Example

<addresses>[]</addresses>

Function

Configures advanced SQL features.

Function

Specifies a list of aggregate listeners to make available to all queries. Each listener must implement the org.apache.openjpa.kernel.exps.AggregateListener interface. For more information, see "kodo.AggregateListeners" in Kodo JPA/JDO Reference for Oracle WebLogic Server.

Example

<aggregate-listeners>
    <custom-aggregate-listener>
        <classname>...</classname>
        <properties>...</properties>
    </custom-aggregate-listener>
</aggregate-listener>

Function

Specifies the number of values to allocate on each database trip. Defaults to 50, meaning the class will set aside the next 50 numbers each time it accesses the sequence table. In this case, Kodo only accesses the database to get new sequence numbers once every 50 sequence number requests.

Example

<allocate>50</allocate>

Function

Flag that specifies whether to immediately throw an exception if you attempt to add an element to a collection or map that is not assignable to the element type declared in metadata.

Example

<assert-allowed-type>false</assert-allowed-type>

Function

Controls whether an object's field values are cleared when entering a transaction. Valid values include:

• datastore (0)—Clear object field values when entering a datastore transaction. This is the default.

• all (1)—Clear object field values when entering any transaction.

Example

<auto-clear>datastore</auto-clear>

Function

Specifies the event on which the managed instances are automatically detached. When specified as a child of the auto-detaches element, valid event types include:

• close (0)—Detach all objects when the PersistenceManager closes. This is the default.

• commit (1)—Detach all objects when a transaction ends.

• nontx-read (2)—Reads outside of a transactions will automatically detach instances before returning them.

Example

<auto-detach>close</auto-detach>

Function

Specifies a list of events on which the managed instances are automatically detached. Specifies one or more auto-detach elements. For more information, see "Automatic Detachment" in Kodo JPA/JDO Reference for Oracle WebLogic Server.

Example

<auto-detaches>
    <auto-detach>close</auto-detach>
</auto-detaches>

Function

Defines the basename of the exported data file to create.

Example

<base-name>base</base-name>

Function

Defines an update manager capable of statement batching, that ignores foreign keys and table-level locking, but optimizes based on the order in which the application has modified objects.

Example

<batching-operation-order-update-manager>
    <maximize-batch-size>true</maximize-batch-size>
</batching-operation-order-update-manager>

Function

Specifies the buffer size of the remote commit provider.

Example

<buffer-size>10</buffer-size>

Function

Defines the cache map used to associate query strings and their parsed form.

Example

<cache-map>
    <cache-size>1000</cache-size>
    <soft-reference-size>-1</soft-reference-size>
</cache-map>

Function

Set the data or query cache size.

Example

<cache-size>1000</cache-size>

Function

Specifies the channel to which you want to log.

Example

<channel>openjpa.Runtime</channel>

Function

Specifies a plugin string describing the kodo.kernel.Seq interface to use to create your own custom generators, in this case kodo.jdbc.kernel.TableJDBCSeq.

The TableJDBCSeq uses a special single-row table to store a global sequence number. If the table does not already exist, it is created the first time you run the mapping tool on a class that requires it. You can also use the class' main method or the sequencetable shell/bat script to manipulate the table; see the TableJDBCSeq.main method Javadoc for usage details.

Example

<class-table-jdbc-seq>
    <type>0</type>
    <allocate>50</allocate>
    <table-name>OPENJPA_SEQUENCES_TABLE</table-name>
    <ignore-virtual>false</ignore-virtual>
    <ignore-unmapped>false</ignore-unmapped>
    <table>OPENJPA_SEQUENCES_TABLE</table>
    <primary-key-column>ID</primary-key-column>
    <use-aliases>false</use-aliases>
    <sequence-column>SEQUENCE_VALUE</sequence-column>
    <increment>1</increment>
</class-table-jdbc-seq>

Function

Name of the class associated with the custom feature.

Function

Specifies a semicolon-separated list of directories or jar archives listed in your classpath. Each directory and jar archive is scanned for annotated JP entities or JDO metadata files based on your metadata factory.

Example

<classpath-scan>build</classpath-scan>

Function

Flag that specifies whether the Tangosol named cache should be completely cleared when the EntityManagerFactory or PersistenceManagerFactory is closed.

Example

<clear-on-close>false</clear-on-close>

Function

A plugin string describing the kodo.kernel.BrokerFactory type to use, in this case remote.

Example

<client-broker-factory/>

Function

Flag that specifies whether the JDO PersistenceManager closes after a managed transaction commits, assuming you have invoked the close method.

If set to false, then the PersistenceManager will not close. This means that objects passed to a processing tier in the same JVM will still be usable, as their owning PersistenceManager will still be open. This behavior is not in strict compliance with the JDO specification, but is convenient for applications that were coded against Kodo 2.x, which did not close the PersistenceManager in these situations.

Example

<close-on-managed-commit>false</close-on-managed-commit>

Function

Configures Kodo to share commit notifications among persistenceManagerFactories in a cluster.

Example

<cluster-remote-commit-provider>
    <name>kodo.RemoteCommitProvider</name>
    <buffer-size>10</buffer-size>
    <recover-action>none</recover-action>
</cluster-remote-commit-provider>

Function

Specifies the Apache Jakarta Commons Logging thin library for issuing log messages. The Commons Logging libraries act as a wrapper around a number of popular logging APIs, including the Jakarta Log4J project, and the native java.util.logging package in JDK 1.4. If neither of these libraries are available, then logging will fall back to using simple console logging.

Example

<commons-log-factory/>

Function

Configure backwards compatibility settings for certain runtime behaviors.

Example

<compatibility>
    <copy-object-ids>false</copy-object-ids>
    <close-on-managed-commit>true</close-on-managed-commit> 
    <validate-true-checks-store>false</validate-true-checks-store>
    <validate-false-returns-hollow>true</validate-false-returns-hollow>
    <strict-identity-values>false</strict-identity-values>
    <quoted-numbers-in-queries>false</quoted-numbers-in-queries>
</compatibility>

Function

Defines the concurrent hash map used to associate query strings and their parsed form.

Example

<concurrent-hash-map>
    <max-size>2147483647</max-size>
</concurrent-hash-map>

Function

A plugin string describing org.apache.openjpa.lib.jdbc.ConnectionDecorator implementations to install on the connection factory. Specify one or more custom-connection-decorator elements.

These decorators can wrap connections passed from the underlying DataSource to add functionality. Kodo will pass all connections through the list of decorators before using them.

Example

<connection-decorators>
    <custom-connection-decorator> 
        <classname>...</classname> 
        <properties>...</properties> 
    </custom-connection-decorator>
</connection-decorators>

Function

Full class name of either the JDBC java.sql.Driver or a javax.sql.DataSource implementation to use to connect to the database.

The following provides sample values:

COM.FirstSQL.Dbcp.DbcpDriver
COM.cloudscape.core.JDBCDriver
COM.ibm.db2.jdbc.app.DB2Driver
COM.ibm.db2.jdbc.net.DB2Driver
centura.java.sqlbase.SqlbaseDriver
com.ddtek.jdbc.db2.DB2Driver
com.ddtek.jdbc.oracle.OracleDriver|
com.ddtek.jdbc.sqlserver.SQLServerDriver
com.ddtek.jdbc.sybase.SybaseDriver
com.ibm.as400.access.AS400JDBCDriver
com.imaginary.sql.msql.MsqlDriver
com.inet.tds.TdsDriver
com.informix.jdbc.IfxDriver
com.internetcds.jdbc.tds.Driver
com.jnetdirect.jsql.JSQLDriver
com.mckoi.JDBCDriver
com.microsoft.jdbc.sqlserver.SQLServerDriver
com.mysql.jdbc.DatabaseMetaData
com.mysql.jdbc.Driver
com.pointbase.jdbc.jdbcUniversalDriver
com.sap.dbtech.jdbc.DriverSapDB
com.sybase.jdbc.SybDriver
com.sybase.jdbc2.jdbc.SybDriver
com.thinweb.tds.Driver
in.co.daffodil.db.jdbc.DaffodilDBDriver
interbase.interclient.Driver
intersolv.jdbc.sequelink.SequeLinkDriver
openlink.jdbc2.Driver
oracle.jdbc.driver.OracleDriver
oracle.jdbc.pool.OracleDataSource
org.axiondb.jdbc.AxionDriver
org.enhydra.instantdb.jdbc.idbDriver
org.gjt.mm.mysql.Driver
org.hsql.jdbcDriver
org.hsqldb.jdbcDriver
org.postgresql.Driver
org.sourceforge.jxdbcon.JXDBConDriver|
postgres95.PGDriver
postgresql.Driver
solid.jdbc.SolidDriver
sun.jdbc.odbc.JdbcOdbcDriver
weblogic.jdbc.mssqlserver4.Driver
weblogic.jdbc.pool.Driver

Example

<connection-driver-name>oracle.jdbc.driver.OracleDriver</connection-driver-name>

Function

The connection factory mode to use when integrating with the application server's managed transactions. Valid options include:

• local—Specifies a standard data source under Kodo control.

• managed—Specifies a data source managed by an application server and automatically enlisted in global transactions.

Example

<connection-factory-mode>local</connection-factory-mode>

Function

The JNDI location of a javax.sql.DataSource to use to connect to the database.

Example

<connection-factory-name>java:/OracleSource</connection-factory-name>

Function

A plugin string listing properties for configuration of the javax.sql.DataSource, described at http://docs.oracle.com/javase/6/docs/api/javax/sql/DataSource.html, in use.

Example

<connection-factory-properties>
    <property>
        <name>QueryTimeout</name>
        <value>5000</value>
        <name>MaxIdle</name>
        <value>1</value>
    </property>
</connection-factory-properties>

Function

The JNDI location of an unmanaged javax.sql.DataSource to use to connect to the database.

Example

<connection-factory2-name>java:/OracleXASource</connection-factory2-name>

Function

Properties used to configure the javax.sql.DataSource, described at http://docs.oracle.com/javase/6/docs/api/javax/sql/DataSource.html, used as the unmanaged ConnectionFactory.

Example

<connection-factory2-properties>
    <property>
        <name>MaxActive</name>
        <value>20</value>
        <name>MaxIdle</name>
        <value>1</value>
    </property>
</connection-factory2-properties>

Function

Password for the user specified by connection-user-name.

Example

<connection-password>tiger</connection-password>

Function

A plugin string listing properties to configure the driver listed in the connection-driver-name element. If the given driver class is a DataSource, these properties will be used to configure the bean properties of the DataSource.

Example

<connection-properties>
    <property>
        <name>PortNumber</name>
        <value>1521</value>
    </property>
    <property>
        <name>ServerName</name>
        <value>saturn</value>
    </property>
    <property>
        <name>DatabaseName</name>
        <value>solarisid</value>
    </property>
    <property>
        <name>DriverType</name>
        <value>thin</value>
    </property>
</connection-properties>

Function

Controls how Kodo uses datastore connections. Valid values include:

• always—Each EntityManager or PersistenceManager obtains a single connection and uses it until the EntityManager or PersistenceManager closes.

• on-demand—Connection is obtained only when needed. This option is equivalent to the transaction option when datastore transactions are used. For optimistic transactions, though, it means that a connection will be retained only for the duration of the datastore flush and commit process.

• persistence-manager—Connection is obtained from the persistence manager.

• transaction—Connection is obtained when each transaction begins (optimistic or datastore), and is released when the transaction completes. Non-transactional connections are obtained on-demand.

Example

<connection-retain-mode>on-demand</connection-retain-mode>

Function

The JDBC URL for the database.

The following provides possible values:

jdbc:JSQLConnect://<hostname>/database=<database>
jdbc:cloudscape:<database>;create=true
jdbc:daffodilDB_embedded:<database>;create=true
jdbc:datadirect:db2://<hostname>:50000;databaseName=<database>
jdbc:datadirect:oracle://<hostname>:1521;SID=<database>;MaxPooledStatements=0
jdbc:datadirect:sqlserver://<hostname>:1433;SelectMethod=cursor;DatabaseName=<database>
jdbc:datadirect:sybase://<hostname>:5000 
jdbc:db2://<hostname>/<database>
jdbc:dbaw://<hostname>:8889/<database>
jdbc:hsqldb:<database>
jdbc:idb:<database>.properties
jdbc:inetdae:<hostname>:1433
jdbc:informix-sqli://<hostname>:1526/<database>:INFORMIXSERVER=<database>
jdbc:interbase://<hostname>//<database>.gdb
jdbc:microsoft:sqlserver://<hostname>:1433;DatabaseName=<database>;SelectMethod=cursor
jdbc:mysql://<hostname>/<database>?autoReconnect=true
jdbc:odbc:<database>
jdbc:openlink://<hostname>/DSN=SQLServerDB/UID=sa/PWD=
jdbc:oracle:thin:@<hostname>:1521:<database>
jdbc:postgresql://<hostname>:5432/<database>
jdbc:postgresql:net//<hostname>/<database>
jdbc:sequelink://<hostname>:4003/[Oracle]
jdbc:sequelink://<hostname>:4004/[Informix];Database=<database>
jdbc:sequelink://<hostname>:4005/[Sybase];Database=<database>
jdbc:sequelink://<hostname>:4006/[SQLServer];Database=<database>
jdbc:sequelink://<hostname>:4011/[ODBC MS Access];Database=<database>
jdbc:solid://<hostname>:<port>/<UID>/<PWD>
jdbc:sybase:Tds:<hostname>:4100/<database>?ServiceName=<database>
jdbc:twtds:sqlserver://<hostname>/<database>
jdbc:weblogic:mssqlserver4:<database>@<hostname>:1433

Example

<connection-url>
jdbc:oracle:thin:@<hostname>:1521:<database>
</connection-url>

Function

Username to use when connecting to the data source specified by connection-url.

Example

<connection-user-name>scott</connection-user-name>

Function

Full class name of either the JDBC java.sql.Driver or a javax.sql.DataSource implementation to use to connect to the unmanaged database.

Example

<connection2-driver-name>oracle.jdbc.driver.OracleDriver</connection2-driver-name>

Function

Password for the unmanaged data source specified by connection2-url.

Example

<connection2-password>tiger</connection2-password>

Function

Properties for the unmanaged data source specified by connection2-driver-name.

Example

<connection2-properties>
    <property>
        <name>PortNumber</name>
        <value>1521</value>
    </property>
    <property>
        <name>ServerName</name>
        <value>saturn</value>
    </property>
    <property>
        <name>DatabaseName</name>
        <value>solarisid</value>
    </property>
    <property>
        <name>DriverType</name>
        <value>thin</value>
    </property>
</connection2-properties>

Function

The JDBC URL for the unmanaged datasource.

Example

<connection2-url>jdbc:oracle:thin:@CROM:1521:KodoDB</connection2-url>

Function

Username to use when connecting to the data source specified by connection2-driver-name.

Example

<connection2-user-name>scott</connection2-user-name>

Function

Flag that specifies whether to include the names of foreign key and unique constraints in all generated mappings.

Example

<constraint-names>false</constraint-names>

Function

Defines the standard update manager, capable of statement batching and foreign key constraint evaluation.

Example

<constraint-update-manager>
    <maximize-batch-size>true</maximize-batch-size>
</constraint-update-manager>

Function

Flag that specifies whether to copy oid objects before returning them to you. Kodo versions prior to 3.0 always copied oid objects before returning them to you. This prevents possible errors resulting from you mutating the oid object by reference, but was not very efficient for the majority of users who do not modify oid instances. Thus Kodo 3.0 and higher does not copy oids by default. Set this property to true to force Kodo to copy the oids.

Example

<copy-object-ids>false</copy-object-ids>

Function

Defines a custom aggregate listener. Each listener must implement the org.apache.openjpa.kernel.exps.AggregateListener interface.

Example

<aggregate-listeners>
    <custom-aggregate-listener>
        <classname>...</classname>
        <properties>...</properties>
    </custom-aggregate-listener>
</aggregate-listener>

Function

Enables you to specify a custom broker factory.

Example

<custom-broker-factory>
    <classname>...</classname>
    <properties>...</properties>
</custom-broker-factory>

Function

Enables you to define a custom broker implementation.

Example

<custom-broker-impl>
    <classname>...</classname>
    <properties>...</properties>
</custom-broker-impl> 

Function

Enables you to define a custom class resolver for class name resolution.

Example

<custom-class-resolver>
    <classname>...</classname>
    <properties>...</properties>
</custom-class-resolver> 

Function

Enables you to define your own custom compatibility flag.

Example

<custom-compatibility>
    <classname>...</classname>
    <properties>...</properties>
</custom-compatibility> 

Function

Enables you to define a custom org.apache.openjpa.lib.jdbc.ConnectionDecorator implementation to install on all connection pools.

Example

<connection-decorators>
    <custom-connection-decorator> 
        <classname>...</classname> 
        <properties>...</properties> 
    </custom-connection-decorator>
</connection-decorators>

Function

Enables you to define a custom data cache.

Example

<data-caches>
    <custom-data-cache>
        <name>...</name>
        <classname>...</classname>
        <properties>...</properties>
    </custom-data-cache>
</data-caches>

Function

Enables you to define a custom data cache manager.

Example

<custom-data-cache-manager>
    <classname>...</classname>
    <properties>...</properties>
</custom-data-cache-manager>

Function

Enables you to define a custom detach state.

Example

<custom-detach-state> 
    <classname>...</classname
    <properties>...</properties>
</custom-detach-state>

Function

Enables you to define a custom dictionary. For more information, see "Custom Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

<custom-dictionary>
   <name>custom-dictionary</name
   <classname>..</classname>
   <properties>...</properties>
</custom-dictionary>

Function

Enables you to define a custom datasource driver.

Example

<custom-driver-data-source> 
    <classname>...</classname
    <properties>...</properties>
</custom-driver-data-source>

Function

Enables you to define a custom filter listener.

Example

<filter-listeners>
    <custom-filter-listener> 
        <classname>...</classname> 
        <properties>...</properties> 
    </custom-filter-listener>
</filter-listeners>

Function

Enables you to define a custom JDBC listener.

Example

<jdbc-listeners>
    <custom-jdbc-listener> 
        <classname>...</classname> 
        <properties>...</properties> 
    </custom-jdbc-listener>
</jdbc-listeners>

Function

Enables you to define a custom lock manager.

Example

<custom-lock-manager>
    <classname>...</classname>
    <properties>...</properties>
</custom-lock-manager>

Function

Enables you to define a custom log file.

Example

<custom-log>
    <classname>...</classname>
    <properties>...</properties>
</custom-log>

Function

Enables you to define custom mapping defaults.

Example

<custom-mapping-defaults> 
    <classname>...</classname
    <properties>...</properties>
</custom-mapping-defaults>

Function

Specifies a custom mapping factory.

Example

<custom-mapping-factory/>

Function

Enables you to specify a custom metadata factory.

Example

<custom-meta-data-factory>
    <classname>...</classname>
    <properties>...</properties>
</custom-meta-data-factory>

Function

Enables you to specify a custom metadata repository. For more information, see "Metadata Factory" in the Kodo JPA/JDO Reference for Oracle WebLogic Server.

Example

<custom-meta-data-repository>
    <classname>...</classname>
    <properties>...</properties>
</custom-meta-data-repository>

Function

Enables you to define a custom orphaned key action.

Example

<custom-orphaned-key-action>
    <channel>openjpa.Runtime</channel>
    <level>4</level>
    <classname>...</classname>
    <properties>...</properties>
</custom-orphaned-key-action>

Function

Enables you to define a custom persistence server.

Example

<custom-persistence-server>
    <classname>...</classname>
    <properties>...</properties>
</custom-persistence-server>

Function

Enables you to define a custom proxy manager.

Example

<custom-proxy-manager> 
    <classname>...</classname
    <properties>...</properties>
</custom-proxy-manager>

Function

Enables you to define a custom query compilation cache.

Example

<custom-query-compilation-cache> 
    <classname>...</classname
    <properties>...</properties>
</custom-query-compilation-cache>

Function

Enables you to specify a custom remote commit provider.

Example

<custom-remote-commit-provider>
    <name>kodo.RemoteCommitProvider</name>
    <classname>...</classname>
    <properties>...</properties>
</custom-remote-commit-provider>

Function

Enables you to specify a custom savepoint manager.

Example

<custom-savepoint-manager>
    <classname>...</classname>
    <properties>...</properties>
</custom-savepoint-manager>

Function

Specifies a custom schema factory.

Example

<custom-schema-factory>
    <classname>...</classname>
    <properties>...</properties>
</custom-schema-factory>

Function

Enables you to define a custom generator.

Example

<custom-seq> 
    <classname>...</classname
    <properties>...</properties>
</custom-seq>

Function

Enables you to define a custom SQL factory.

Example

<custom-sql-factory>
    <classname>...</classname>
    <properties>...</properties>
</custom-sql-factory>

Function

Enables you to define a custom update manager to use to flush persistent object changes to the datastore.

Example

<custom-update-manager>
   <classname>..</classname>
   <properties>...</properties>
</custom-update-manager>

Function

Specifies plugins used to cache data loaded from the data store. Must implement org.apache.openjpa.datacache.DataCache.

Example

<data-caches>
    <default-data-cache>...</default-data-cache>
    <kodo-concurrent-data-cache>...</kodo-concurrent-data-cache>
    <gem-fire-data-cache>...</gem-fire-data-cache>
    <lru-data-cache>...</lru-data-cache>
    <tangosol-data-cache>...</tangosol-data-cache>
    <custom-data-cache>...</custom-data-cache>
</data-caches>

Function

Enables the kodo.datacache.DataCacheManager that manages the system data caches.

Example

<data-cache-manager-impl/>

Function

Specifies the amount of time in milliseconds that a class' data is valid. A value of -1 specifies no expiration.

Example

<data-cache-timeout>-1</data-cache-timeout>

Function

Defines the configuration values for the DB2 Dictionary persistence plugin. For a complete description of each of the values that you can specify, see "DB2 Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help

Example

The db2-dictionary element shares the same subelements as "access-dictionary".

Function

Specifies the default access type. Valid values include:

• FIELD—Injects state directly into your persistent fields, and retrieves changed state from your fields as well.

• PROPERTY—Retrieves and loads state through JavaBean "getter" and "setter" methods.

Example

<default-access-type>FIELD</default-access-type>

Function

Specifies a plugin string describing the kodo.kernel.BrokerFactory type to use, in this case the default, which is JDBC.

Example

<default-broker-factory/>

Function

Specifies a plugin string describing the kodo.kernel.Broker type to use at runtime, in this case the default.

Example

<default-broker-impl/>

Function

Specifies a plugin string describing the kodo.util.ClassResolver implementation to use for class name resolution, in this case the default. You may wish to plug in your own resolver if you have special class loading needs.

Example

<default-class-resolver/>

Function

Sets the default compatibility settings.

Example

<default-compatibility/>

Function

Defines the default data cache.

Example

<data-caches>
    <default-data-cache> 
        <name>kodo.DataCache</name> 
    </default-data-cache>
</data-caches>

Function

Specifies the default detached state, in this case loaded.

Example

<default-detach-state/> 

Function

Specifies a plugin string describing the kodo.datacache.DataCacheManager that manages the system data caches, in this case the default.

Example

<default-data-cache-manager>...</default-data-cache-manager>

Function

Specifies the default kodo.jdbc.schema.DriverDataSource implementation to use to wrap JDBC Driver classes with javax.sql.DataSource instances. The provided default implementation, kodo.jdbc.schema.KodoPoolingDataSource, will perform connection pooling.

Example

<default-driver-data-source/>

Function

Specifies the default logging level of unconfigured channels.

Example

<default-level>INFO</default-level>

Function

Specifies to use the default lock manager.

Example

<default-lock-manager/>

Function

Specifies a plugin string describing the kodo.jdbc.meta.MappingDefaults to use to define default column names, table names, and constraints for your persistent classes.

Example

<default-mapping-defaults>jpa</default-mapping-defaults>

Function

Specifies a plugin string describing the kodo.meta.MetaDataFactory type to use, in this case the default, which is kodo.jdo.JDOMetaDataFactory.

Example

<default-meta-data-factory/>

Function

Specifies a plugin string describing the kodo.meta.MetaDataRepository to use to store the metadata for your persistent classes, in this case the default.

Example

<default-meta-data-repository/>

Function

Specifies a plugin string describing the kodo.event.OrphanedKeyAction to invoke when Kodo discovers an orphaned datastore key, in this case the default which is kodo.event.LogOrphanedKeyAction. In this case, Kodo logs a message for each orphaned key.

Example

<default-orphaned-key-action>
    <channel>openjpa.Runtime</channel>
    <level>4</level>
</default-orphaned-key-action>

Function

Specifies a plugin string describing the kodo.util.ProxyManager to use for proxying mutable second class objects, in this case the default, which is kodo.util.ProxyManagerImpl.

Example

<default-proxy-manager/>

Function

Specifies a plugin string describing the Map used to associate query strings and their parsed form, in this case the default.

Example

<default-query-compilation-cache/>

Function

Specifies a plugin string describing the kodo.kernel.SavepointManager to use for managing transaction savepoints, in this case the default which is kodo.kernel.InMemorySavepointManager. This plugin stores all state, including field values, in memory. Because of this behavior, each set savepoint is designed for small to medium transactional object counts.

Example

<default-savepoint-manager/>

Function

Specifies a plugin string describing the kodo.jdbc.schema.SchemaFactory to use to store and retrieve information about the database schema, in this case the default which is kodo.jdbc.schema.DynamicSchemaFactory.

The DynamicSchemaFactory is the most performant schema factory, because it does not validate mapping information against the database. Instead, it assumes all object-relational mapping information is correct, and dynamically builds an in-memory representation of the schema from your mapping metadata. When using this factory, it is important that your mapping metadata correctly represent your database's foreign key constraints so that Kodo can order its SQL statements to meet them.

Example

<default-schema-factory/>

Function

Specifies a plugin string describing the kodo.jdbc.SQLFactory to use to abstract common SQL constructs, in this case the default.

Example

<default-meta-data-factory/>

Function

Specifies to use the default update manager, kodo.jdbc.kernel.ConstraintUpdateManager.

Example

<default-update-manager/>

Function

Specifies the mapping defaults for JDO 1.0.

Example

The deprecated-jdo-mapping-defaults element shares the same subelements as mapping-defaults-impl.

Function

Specifies a plugin string describing the kodo.meta.MetaDataFactory type to use, in this case kodo.jdo.DeprecatedJDOMetaDataFactory.

Example

<deprecated-jdo-meta-data-factory>
    <use-schema-validation>false</use-schema-validation>
    <urls>t3://localhost:7001/metadata.jar</urls>
    <files>com/file1;com/file2</files>
    <classpath-scan>build</classpath-scan>
    <types>classname1;classname2</types>
    <store-mode>1</store-mode>
    <strict>false</strict>
    <resources>com/aaa/package.jdo;com/bbb/package.jdo</resources>
    <scan-top-down>false</scan-top-down>
</deprecated-jdo-meta-data-factory>

Function

Configures the Derby Dictionary. For a complete description of each of the values that you can specify, see "Derby Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

The derby-dictionary element shares the same subelements as, plus the following subelement (default shown):

<derby-dictionary>
...
   <shutdown-on-close>true</shutdown-on-close>
</derby-dictionary>

Function

Sets the detach state to all to detach all fields and relations. Be very careful when using this mode; if you have a highly-connected domain model, you could end up bringing every object in the database into memory.

Example

<detach-options-all> 
    <detached-state-manager>true</detached-state-manager>
    <detached-state-transient>false</detached-state-transient>
    <access-unloaded>true</access-unloaded>
    <detached-state-field>true</detached-state-field>
</detach-options-all>

Function

Sets the detach state to detach all fields and relations in the default fetch group, and any other fetch groups that you have added to the current fetch configuration.

Example

<detach-options-fetch-groups> 
    <detached-state-manager>true</detached-state-manager>
    <detached-state-transient>false</detached-state-transient>
    <access-unloaded>true</access-unloaded>
    <detached-state-field>true</detached-state-field>
</detach-options-fetch-groups>

Function

Sets the detach state to detach all fields and relations that are already loaded, but do not include unloaded fields in the detached graph. This is the default.

Example

<detach-options-loaded> 
    <detached-state-manager>true</detached-state-manager>
    <detached-state-transient>false</detached-state-transient>
    <access-unloaded>true</access-unloaded>
    <detached-state-field>true</detached-state-field>
</detach-options-loaded>

Function

Configures the detach state. Valid values include:

• 1—(loaded) Detach all fields and relations that are already loaded, but do not include unloaded fields in the detached graph.

• 2—(fetch-groups) Detach all fields and relations in the current fetch configuration.

• 3—(all) Detach all fields and relations. Be very careful when using this mode; if you have a highly-connected domain model, you could end up bringing every object in the database into memory.

Any field that is not included in the set determined by the detach mode is set to its Java default value in the detached instance.

Example

<detach-state>1</detach-state>

Function

Flag that specifies whether Kodo should take advantage of a detached state field to make the attach process more efficient. This field is added by the enhancer and is not visible to your application.

Example

<detached-state-field>true</detached-state-field>

Function

Flag that specifies whether to use a detached state manager. A detached state manager makes attachment much more efficient. Like a detached state field, however, it breaks serialization compatibility with the unenhanced class if it is not transient.

This setting piggybacks on the detached-state-field element. If your detached state field is transient, the detached state manager will also be transient. If the detached state field is disabled, the detached state manager will also be disabled. This is typically what you want.

By setting the detach-state-field element to true (or transient) and setting this property to false, however, you can use a detached state field without using a detached state manager. This may be useful for debugging or for legacy Kodo users who find differences between Kodo's behavior with a detached state manager and Kodo's older behavior without one.

Example

<detached-state-manager>true</detached-state-manager>

Function

Flag that specifies whether to use a transient detached state field. Setting this to true provides the benefits of a detached state field to local objects that are never serialized, but retains serialization compatibility for client tiers without access to the enhanced versions of your classes.

Example

<detached-state-transient>false</detached-state-transient>

Function

Flag that specifies whether to use a non-transient detached state field so that objects crossing serialization barriers can still be attached efficiently. This requires, however, that your client tier have the enhanced versions of your classes and the Kodo libraries.

Example

<detached-new>true</detached-new>

Function

String that is prepended to all log messages. The kodo.ID property is used by default, if specified.

Example

<diagnostic-context>KodoID</diagnostic-context>

Function

Flag that specifies whether to dynamically generate customized structs to hold persistent data. Both the Kodo data cache and the remote framework rely on data structs to cache and transfer persistent state. With dynamic structs, Kodo can customize data storage for each class, eliminating the need to generate primitive wrapper objects. This saves memory and speeds up certain runtime operations.

The cost is a longer warm-up time for the application—generating and loading custom classes into the JVM takes time. Therefore, only set this property to true if you have a long-running application where the initial cost of class generation is offset by memory and speed optimization over time.

Example

<dynamic-data-structs>false</dynamic-data-structs>

Function

Specifies a plugin string describing the kodo.jdbc.schema.SchemaFactory to use to store and retrieve information about the database schema, in this case the default which is kodo.jdbc.schema.DynamicSchemaFactory.

The DynamicSchemaFactory is the most performant schema factory, because it does not validate mapping information against the database. Instead, it assumes all object-relational mapping information is correct, and dynamically builds an in-memory representation of the schema from your mapping metadata. When using this factory, it is important that your mapping metadata correctly represent your database's foreign key constraints so that Kodo can order its SQL statements to meet them.

Example

<dynamic-schema-factory/>

Function

Configures eager fetching. Eager fetching is the ability to efficiently load subclass data and related objects along with the base instances being queried.

You can set this value to one of the following:

• join—In this mode, Kodo joins to-one relations in the configured fetch groups. If Kodo is loading data for a single instance, then Kodo will also join to any collection field in the configured fetch groups. When loading data for multiple instances, though, (such as when executing a Query) Kodo will not join to collections by default. Instead, Kodo defaults to parallel mode for collections, as described below. You can force Kodo to use a join rather than parallel mode for a collection field using the metadata extension.

  Under join mode, Kodo uses a left outer join (or inner join, if the relations' field metadata declares the relation non-nullable) to select the related data along with the data for the target objects. This process works recursively for to-one joins, so that if Person has an Address, and Address has a TelephoneNumber, and the fetch groups are configured correctly, Kodo might issue a single select that joins across the tables for all three classes. To-many joins can not recursively spawn other to-many joins, but they can spawn recursive to-one joins.

  Under the join subclass fetch mode, subclass data in joined tables is selected by outer joining to all possible subclass tables of the type being queried. Unjoined subclass data is selected with a SQL UNION where possible. As you'll see below, subclass data fetching is configured separately from relation fetching, and can be disabled for specific classes.

• multiple—Same as parallel.

• none—No eager fetching is performed. Related objects are always loaded in an independent select statement. No joined subclass data is loaded unless it is in the table(s) for the base type being queried. Unjoined subclass data is loaded using separate select statements rather than an SQL UNION operation.

• parallel—Under this mode, Kodo selects to-one relations and joined collections as outlined in the join mode description above. Unjoined collection fields, however, are eagerly fetched using a separate select statement for each collection, executed in parallel with the select statement for the target objects. The parallel selects use the WHERE conditions from the primary select, but add their own joins to reach the related data. Thus, if you perform a query that returns 100 Company objects, where each company has a list of Employee objects and Department objects, Kodo will make three queries. The first will select the company objects, the second will select the employees for those companies, and the third will select the departments for the same companies. Just as for joins, this process can be recursively applied to the objects in the relations being eagerly fetched. Continuing our example, if the Employee class had a list of Projects in one of the fetch groups being loaded, Kodo would execute a single additional select in parallel to load the projects of all employees of the matching companies.

  Using an additional select to load each collection avoids transferring more data than necessary from the database to the application. If eager joins were used instead of parallel select statements, each collection added to the configured fetch groups would cause the amount of data being transferred to rise dangerously, to the point that you could easily overwhelm the network.

  Polymorphic to-one relations to table-per-class mappings use parallel eager fetching because proper joins are impossible. You can force other to-one relations to use parallel rather than join mode eager fetching using the metadata extension.

  Setting your subclass fetch mode to parallel affects table-per-class and vertical inheritance hierarchies. Under parallel mode, Kodo issues separate selects for each subclass in a table-per-class inheritance hierarchy, rather than UNIONing all subclass tables together as in join mode. This applies to any operation on a table-per-class base class: query, by-id lookup, or relation traversal.

  When dealing with a vertically-mapped hierarchy, on the other hand, parallel subclass fetch mode only applies to queries. Rather than outer-joining to subclass tables, Kodo will issue the query separately for each subclass. In all other situations, parallel subclass fetch mode acts just like join mode in regards to vertically-mapped subclasses.

  When Kodo knows that it is selecting for a single object only, it never uses parallel mode, because the additional selects can be made lazily just as efficiently. This mode only increases efficiency over join mode when multiple objects with eager relations are being loaded, or when multiple selects might be faster than joining to all possible subclasses.

• single—Same as join.

Example

<eager-fetch-mode>parallel</eager-fetch-mode>

Function

Configures the Empress Dictionary. For a complete description of each of the values that you can specify, see "Empress Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

The empress-dictionary element shares the same subelements as access-dictionary, plus the following sub-element (default shown):

<empress-dictionary>
...
   <allow-concurrent-read>false</allow-concurrent-read>
</empress-dictionary>

Function

Flag that specifies whether the LogMBean should be registered.

Example

<EnableLogMBean>true</EnableLogMBean>

Function

Flag that specifies whether the RuntimeMBean should be registered.

Example

<EnableRuntimeMBean>true</EnableRuntimeMBean>

Function

Flag that specifies whether to evict data from the data cache at specific times. You defined the eviction schedule using the eviction-schedule element.

Example

<evict-from-data-cache>true</evict-from-data-cache>

Function

You can clear a data cache at specific times. The EvictionSchedule property of Kodo's cache implementation accepts a cron style eviction schedule. The format of this property is a whitespace-separated list of five tokens. You can use the * symbol (asterisk) as a wildcard to match all values. The following lists the tokens in the order that they must be specified:

• Minute

• Hour of Day

• Day of Month

• Month

• Day of Week

Example

The following setting schedules the default cache to evict values from the cache at 15 and 45 minutes past 3:00 pm on Sunday.

<eviction-schedule>15,45 15 * * 1</eviction-schedule>

Function

Specifies a plugin string describing the kodo.event.OrphanedKeyAction to invoke when Kodo discovers an orphaned datastore key, in this case kodo.event.ExceptionOrphanedKeyAction. In this case, Kodo throws an exception for each orphaned key. In JPA, the exception will be javax.persistence.EntityNotFoundException. In JDO, the exception type will be javax.jdo.JDOObejctNotFoundException.

Example

<exception-orphaned-key-action/>

Function

Specifies the number of time to attempt to reconnect if the JMS system notifies Kodo of a serious connection error. A value of 0 (the default) indicates that Kodo will log the error but otherwise ignore it, hoping the connection is still valid.

Example

<exception-reconnect-attempts>0<exception-reconnect-attempts>

Function

Configure the execution context name provider.

Example

<execution-context-name-provider>
    <stack-execution-context-name-provider>...
    </stack-execution-context-name-provider>
    <transaction-name-execution-context-name-provider>...
    </transaction-name-execution-context-name-provider>
    <user-object-execution-context-name-provider>...
    </user-object-execution-context-name-provider>
</execution-context-name-provider>

Function

Configure export profiling data.

Example

<profiling>
    <export-profiling>
        <interval-millis>-1</interval-millis>
        <base-name>name</base-name>
    </export-profiling>
</profiling>

Function

A plugin string describing the kodo.meta.MetaDataFactory to use to store and retrieve object-relational mapping information for your persistent classes. This setting is valid for JDO 1.0.

Example

<extension-deprecated-jdo-mapping-factory>
    <use-schema-validation>true</use-schema-validation>
    <urls>t3://localhost:7001/metadata.jar</urls>
    <files>com/file1;com/file2</files>
    <classpath-scan>build</classpath-scan>
    <types>classname1;classname2</types>
    <store-mode>1</store-mode>
    <strict>false</strict>
    <resources>com/aaa/package.jdo;com/bbb/package.jdo</resources>
    <scan-top-down>false</scan-top-down>
</extension-deprecated-jdo-mapping-factory>

Function

The number of rows to fetch at one time when scrolling through a result set. The fetch size can also be set at runtime.

Example

<fetch-batch-size>-1</fetch-batch-size>

Function

The expected order in which query result lists are accessed. This value affects the type of data structure Kodo uses to store the results, and is passed to the JDBC driver in case it can optimize for certain access patterns. This element accepts the following values, each of which corresponds exactly to the same-named java.sql.ResultSet FETCH constant:

• forward—Query results are listed in order. This is the default.

• reverse—Query results are listed in reverse order.

• unknown—The order is not specified.

This property can also be varied at runtime.

Example

<fetch-direction>forward</fetch-direction>

Function

Name of a fetch group. Fetch group names are global, and are expected to be shared among classes. For example, a shopping website may use a detail fetch group in each product class to efficiently load all the data needed to display a product's "detail" page. The website might also define a sparse list fetch group containing only the fields needed to display a table of products, as in a search result.

The following names are reserved for use by Kodo: default, values, all, none, and any name beginning with jdo, ejb, or kodo.

Example

<fetch-groups>
    <fetch-group>detail</fetch-group>
</fetch-groups>

Function

Define one or more custom fetch groups.

By default, Kodo places any field that is eagerly loaded according to the JPA metadata rules into the built-in default fetch group. You may define your own named fetch groups and activate or deactivate them at runtime. Kodo will eagerly-load the fields in all active fetch groups when loading objects from the datastore.

Example

<fetch-groups>
    <fetch-group>detail</fetch-group>
</fetch-groups>

Function

Flag that specifies whether to enable field override.

Example

<field-override>true</field-override>

Function

If the parent element is file-schema-factory, specifies the resource name of the XML schema file. By default, the factory looks for a resource called package.schema located in any top-level directory of the CLASSPATH or in the top level of any JAR in your CLASSPATH.

If the parent element is log-factory-impl, specifies the name of the file to which messages are logged. Specify stdout or stderr to log messages to standard out and standard error, respectively. The default is stderr.

Example

<file>stdout</file>

Function

Specifies the resource name of the XML schema file. By default, the factory looks for a resource called package.schema located in any top-level directory of the CLASSPATH or in the top level of any JAR in your CLASSPATH.

Example

<file-name>package.schema</file-name>

Function

Specifies a plugin string describing the kodo.jdbc.schema.SchemaFactory to use to store and retrieve information about the database schema, in this case kodo.jdbc.schema.FileSchemaFactory.

This factory is a lot like the table-schema-factory, and has the same advantages and disadvantages. Instead of storing its XML schema definition in a database table, though, it stores it in a file.

Example

<file-schema-factory>
    <file-name>package.schema</file-name>
    <file>package.schema</file>
</file-schema-factory>

Function

Specifies a semicolon-separated list of metadata files or JAR archives. Each jar archive will be scanned for annotated JPA entities or JDO metadata files based on your metadata factory.

Example

<files>com/file1;com/file2</files>

Function

Defines one or more full plugin strings for custom kodo.FilterListeners to make available to all queries, in addition to the standard set of listeners. You can also add filter listeners to individual queries.

Example

<filter-listeners>
    <custom-filter-listener>detail</custom-filter-listener>
</filter-listeners>

Function

Flag that specifies whether to read automatically foreign key information during schema validation.

Example

<foreign-keys>false</foreign-keys>

Function

Specifies the format.

Function

Configuration values for the FoxPro Dictionary persistence plugin. For a complete description of each of the values that you can specify, see "FoxPro Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

The foxpro-dictionary element shares the same subelements as access-dictionary.

Function

Flag that specifies whether to flush any changes made in the current transaction to the datastore before executing a query. Valid values include:

• true—Always flush rather than executing the query in-memory. If the current transaction is optimistic, Kodo will begin a non-locking datastore transaction. This is the default.

• false—Never flush before a query.

• with-connection—Flush only if the EntityManager or PersistenceManager has already established a dedicated connection to the datastore, otherwise execute the query in-memory.

  This option is useful if you use long-running optimistic transactions and want to ensure that these transactions do not consume database resources until commit. Kodo's behavior with this option is dependent on the transaction status and mode, as well as the configured connection retain mode described earlier in this section.

Example

<flush-before-queries>true</flush-before-queries>

Function

Integrates with GemStone's GemFire v5.0.1 caching system.

Example

<data-caches>
    <gem-fire-data-cache>
        <name>kodo.DataCache</name>
        <gem-fire-cache-name>root/kodo-data-cache</gem-fire-cache-name>
        <eviction-schedule>15, 45 15 * * 1</eviction-schedule>
    </gem-fire-data-cache>
</data-caches>

Function

GemFire region name.

Example

<gem-fire-data-cache-name>root/kodo-data-cache</gem-fire-data-cache-name>

Function

Enable management and invoke the JMX management console in the local JVM. Supports optional parameters in the Management Group.

Example

<gui-jmx>
    <MBeanServerStrategy>any-create</MBeanServerStrategy>
    <EnableLogMBean>true</EnableLogMBean>
    <EnableRuntimeMBean>true</EnableRuntimeMBean>
</gui-jmx>

Function

Turns on the local profiling GUI.

Example

<profiling>
  <gui-profiling/>
</profiling>

Function

Hostname on which the RMI registry naming service listens. Defaults to localhost.

Example

<Host>localhost</Host>

Function

Specifies the host name of the server. This setting is used by clients, not by the server.

Example

<host>localhost</host>

Function

Configuration values for the HSQL Dictionary persistence plugin. For a complete description of each of the values that you can specify, see "HSQL Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

The hsql-dictionary element shares the same subelements as access-dictionary.

Function

Specifies the URL of the remote server.

Example

<http-transport>
    <url>servlet-url</url>
</http-transport>

Function

Flag that specifies whether to consider modifications to persistent objects made in the current transaction when evaluating queries. Setting this to true allows Kodo to ignore changes and execute the query directly against the datastore. A value of false forces Kodo to consider whether the changes in the current transaction affect the query, and if so to either evaluate the query in-memory or flush before running it against the datastore.

Example

<ignore-changes>false</ignore-changes>

Function

Flag that specifies whether to ignore unmapped base classes and instead use one row per least-derived mapped class.

Example

<ignore-unmapped>false</ignore-unmapped>

Function

Flag that specifies whether to ignore virtual classes.

Example

<ignore-virtual>false</ignore-virtual>

Function

Specifies a plugin string describing the kodo.kernel.SavepointManager to use for managing transaction savepoints, in this case kodo.kernel.InMemorySavepointManager. This plugin stores all state, including field values, in memory. Because of this behavior, each set savepoint is designed for small to medium transactional object counts.

Example

<in-memory-savepoint-manager/>

Function

Specifies the amount of sequence increments.

Example

<increment>1</increment>

Function

Flag that specifies whether to read automatically index information during schema validation.

Example

<indexes>false</indexes>

Function

Configuration values for the Informix Dictionary persistence plugin. For a complete description of each of the values that you can specify, see "Informix Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

The informix-dictionary element shares the same subelements as access-dictionary, plus the following subelements (defaults shown):

<informix-dictionary>
...
   <lock-mode-enabled>false</lock-mode-enabled>
   <lock-wait-seconds>30</lock-wait-seconds>
   <swap-schema-and-catalog>true</swap-schema-and-catalog>
</informix-dictionary>

Function

Specifies the initial sequence value.

Example

<initial-value>1</intial-value>

Function

Number of milliseconds between exports. This value defaults to -1, indicating that there will be a single export upon exit.

Example

<interval-millis>-1</interval-millis>

Function

A plugin string describing a kodo.kernel.InverseManager to use for managing bidirectional relations upon a flush.

Example

<inverse-manager>
    <action>warn</action>
    <manage-lrs>false</manage-lrs>
</inverse-manager>

Function

Configuration values for the JDataStore Dictionary persistence plugin. For a complete description of each of the values that you can specify, see "JDataStore Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

The jdatastore-dictionary element shares the same subelements as access-dictionary.

Function

A plugin string describing the kodo.kernel.BrokerFactory type to use, in this case JDBC.

Example

<jdbc-broker-factory/>

Function

Defines one or more full plugin strings for custom kodo.jdbc.kernel.exps.JDBCFilterListeners to make available to all queries, in addition to the standard set of listeners. You can also add filter listeners to individual queries.

Example

<jdbc-listeners>detail</jdbc-listeners>

Function

Specifies a plugin string describing the kodo.kernel.SavepointManager to use for managing transaction savepoints, in this case the default which is kodo.jdbc.kernel.JDBCSavepointManager. This plugin implements savepoints by issuing a flush to the database.

Example

<jdbc3-savepoint-manager/>

Function

Specifies a plugin string describing the kodo.meta.MetaDataFactory type to use, in this case kodo.jdo.JDOMetaDataFactory.

Example

<jdo-meta-data-factory>
    <use-schema-validation>false</use-schema-validation>
    <urls>t3://localhost:7001/metadata.jar</urls>
    <files>com/file1;com/file2</files>
    <classpath-scan>build</classpath-scan>
    <constraint-names>false</constraint-names>
    <types>classname1;classname2</types>
    <store-mode>1</store-mode>
    <strict>false</strict>
    <resources>com/aaa/package.jdo;com/bbb/package.jdo</resources>
    <scan-top-down>false</scan-top-down>
</jdo-meta-data-factory>

Function

Configures the JMS remote commit provider.

Example

<jms-remote-commit-provider>
    <name>kodo.RemoteCommitProvider</name>
    <topic>topic/KodoCommitProviderTopic</topic>
    <exception-reconnect-attempts>0<exception-reconnect-attempts>
    <topic-connection-factory>java:/ConnectionFactory</topic-connection-factory>
</jms-remote-commit-provider>

Function

Enables for the configuration of management capabilities. For more information, see "Management and Monitoring" in the Kodo JPA/JDO Reference for Oracle WebLogic Server.

Example

<jmx>
    <none-jmx/>
    <local-jmx>...</local-jmx>
    <gui-jmx>...</gui-jmx>
    <jmx2-jmx>...</jmx2-jmx>
    <mx4j1-jmx>...</mx4j1-jmx>
    <wls81-jmx>...</wls81jmx>
</jmx>

Function

Enable remote management via JMX v.1.2 implementations (supporting JSR 160 for remote management). Supports optional parameters in the Management Group and the JSR 160 Group.

Example

<jmx2-jmx>
    <MBeanServerStrategy>any-create</MBeanServerStrategy>
    <EnableLogMBean>true</EnableLogMBean>
    <EnableRuntimeMBean>true</EnableRuntimeMBean>
    <NamingImpl>mx4j.tools.naming.NamingService</NamingImpl>
    <ServiceURL>service:jmx:rmi://localhost/jndi/jmxservice</ServiceURL>
</jmx2-jmx>

Function

JNDI name under which to register the remote JMX adaptor. Defaults to jrmp.

Example

<JNDIName>jrmp</JNDIName>

Function

Configures the kodo.BrokerImpl.

Example

<kodo-broker>
    <large-transaction>false</large-transaction>
    <auto-clear>datastore</auto-clear>
    <detach-state>1</detach-stage>
    <nontransactional-read>true</nontransactional-read>
    <retain-state>false</retain-state>
    <evict-from-data-cache>false</evict-from-data-cache>
    <detached-new>true</detached-new>
    <optimistic>true</optimistic>
    <nontransactional-write>flase</nontransactional-write>
    <sync-with-managed-transacations>false</sync-with-managed-transactions>
    <multithreaded>false</multithreaded>
    <populate-data-cache>true</populate-data-cache>
    <ignore-changes>false</ignore-changes>
    <auto-detach>0</auto-detach>
    <restore-state>1</restore-state>
    <order-dirty-objects>false</other-dirty-objects>
</kodo-broker>

Function

Enables the basic concurrent data cache.

Example

<data-caches>
    <kodo-concurrent-data-cache>
        <name>default</name>
        <cache-size>1000</cache-size>
        <soft-reference-size>0</soft-reference-size>
        <eviction-schedule>15,45 15 * * 1</eviction-schedule>
    </kodo-concurrent-data-cache>
</data-caches>

Function

Enables the kodo.datacache.DataCacheManager that manages the system data caches.

Example

<kodo-data-cache-manager/>

Function

Specifies a plugin string describing the kodo.meta.MetaDataRepository to use.

Example

<kodo-mapping-repository>
    <resolve>3</resolve>
    <validate>7</validate>
    <source-mode>7</source-mode>
</kodo-mapping-repository>

Function

A plugin string describing the kodo.meta.MetaDataFactory to use to store and retrieve object-relational mapping information for your persistent classes. This setting is valid for JPA 1.0.

Example

<kodo-persistence-mapping-factory>
    <urls>t3://localhost:7001/metadata.jar</urls>
    <files>com/file1;com/file2</files>
    <classpath-scan>build</classpath-scan>
    <default-access-type>FIELD</default-access-type>
    <field-override>true</field-override>
    <types>classname1;classname2</types>
    <store-mode>1</store-mode>
    <strict>false</strict>
    <resources>com/aaa/package.jdo;com/bbb/package.jdo</resources>
</kodo-persistence-mapping-factory>

Function

Specifies a plugin string describing the kodo.meta.MetaDataFactory type to use, in this case org.apache.openjpa.persistence.PersistenceMetaDataFactory.

Example

<kodo-persistence-meta-data-factory>
    <urls>t3://localhost:7001/metadata.jar</urls>
    <files>com/file1;com/file2</files>
    <classpath-scan>build</classpath-scan>
    <default-access-type>FIELD</default-access-type>
    <field-override>true</field-override>
    <types>classname1;classname2</types>
    <store-mode>1</store-mode>
    <strict>false</strict>
    <resources>com/aaa/package.jdo;com/bbb/package.jdo</resources>
</kodo-persistence-meta-data-factory>

Function

Configures the kodo.jdbc.schema.KodoPoolingDataSource which by default performs connection pooling.

Example

<kodo-pooling-data-source>
    <connection-user-name>KodoPool</connection-user-name>
    <login-timeout>10</login-timeout>
    <connection-password>password</connection-password>
    <connection-url>jdbc:hsqldb:db-hypersonic</connection-url>
    <connection-driver-name>org.hsqldb.jdbcDrier</connection-driver-name>
</kodo-pooling-data-source>

Function

Specifies a plugin string describing the kodo.jdbc.SQLFactory to use to abstract common SQL constructs.

Example

<kodo-sql-factory>
    <advanced-sql>...</advanced-sql>
</kodo-sql-factory>

Function

Flag that specifies whether the transaction will generate a large number of objects.

Example

<large-transaction>false</large-transaction>

Function

Specifies a plugin string describing the kodo.jdbc.schema.SchemaFactory to use to store and retrieve information about the database schema, in this case kodo.jdbc.schema.LazySchemaFactory.

As persistent classes are loaded by the application, Kodo reads their metadata and object-relational mapping information. This factory uses the java.sql.DatabaseMetaData interface to reflect on the schema and ensure that it is consistent with the mapping data being read. Because the factory does not reflect on a table definition until that table is mentioned by the mapping information, it is referred to as lazy. Use this factory if you want up-front validation that your mapping metadata is consistent with the database during development.

Example

<lazy-schema-factory>
    <foreign-keys>false</foreign-keys>
    <indexes>false</indexes>
    <primary-keys>false</primary-keys>
</lazy-schema-factory>

Function

Specifies the level at which to log. Valid values include: 1 (TRACE), 2 (DEBUG), 3 (INFO), 4 (WARN), and 5 (ERROR).

Example

<level>4</level>

Function

Enabled local management. This setting is suitable for use in JBoss and other environments where all MBeans should be registered with a JMX MBeanServer for either management via a user defined mechanism, or via a mechanism defined by the MBeanServer. Supports optional parameters in the Management Group.

Example

<local-jmx>
    <MBeanServerStrategy>any-create</MBeanServerStrategy>
    <EnableLogMBean>true</EnableLogMBean>
    <EnableRuntimeMBean>true</EnableRuntimeMBean>
</local-jmx>

Function

Enable profiling without export or GUI. Useful when trying to access the ProfilingAgent programmatically.

Example

<profiling>
  <local-profiling/>
</profiling>

Function

Default amount of time that Kodo waits when trying to obtain a lock. A value of -1 specifies that there is no limit.

Example

<lock-timeout>-1</lock-timeout>

Function

Configures the default logging system.

Example

<log-factory-impl>
    <diagnostic-context>ID</diagnostic-context>
    <default-level>INFO</default-level>
    <file>stdout</file>
</log-factory-impl>

Function

Specifies a plugin string describing the kodo.event.OrphanedKeyAction to invoke when Kodo discovers an orphaned datastore key, in this case kodo.event.LogOrphanedKeyAction. In this case, Kodo logs a message for each orphaned key.

Example

<log-orphaned-key-action>
    <channel>openjpa.Runtime</channel>
    <level>4</level>
</log-orphaned-key-action>

Function

Specifies to use Log4J for logging. In a standalone application, Log4J logging levels are controlled by a resource named log4j.properties, which should be available as a top-level resource (either at the top level of a jar file, or in the root of one of the CLASSPATH directories). When deploying to a web or EJB application server, Log4J configuration is often performed in a log4j.xml file instead of a properties file. For further details on configuring Log4J, please see the Log4J 2.x Manual at http://logging.apache.org/log4j/2.x/manual/index.html.

Example

<log4j-log-factory/>

Function

Specifies the login timeout.

Example

<login-timeout>0</login-timeout>

Function

Specifies the size of results sets. This property is only used if you change the fetch batch size from its default of -1 so that Kodo uses the on-demand results loading. Valid values include:

• query—The first time you ask for the size of a query result, Kodo will perform a SELECT COUNT(*) query to determine the number of expected results. Note that depending on transaction status and settings, this can mean that the reported size is slightly different than the actual number of results available. This is the default.

• last—If you have chosen a scrollable result set type, this setting will use the ResultSet.last method to move to the last element in the result set and get its index. Unfortunately, some JDBC drivers will bring all results into memory in order to access the last one. Note that if you do not choose a scrollable result set type, then this will behave exactly like unknown. The default result set type is forward-only, so you must change the result set type in order for this property to have an effect.

• unknown—Kodo returns Integer.MAX_VALUE as the size for any query result that uses on-demand loading.

Example

<lrs-size>query</lrs-size>

Function

Sets the least-recently-used (LRU) data caching option.

Example

<data-caches>
    <lru-data-cache>
        <name>kodo.DataCache</name>
        <cache-size>1000</cache-size>
        <soft-reference-size>0</soft-reference-size>
        <eviction-schedule>15,45 15 * * 1</eviction-schedule>
    </lru-data-cache>
</data-caches>

Function

Flag that specifies whether large result set fields are included from management.

Example

<manage-lrs>false</manage-lrs>

Function

When a child element of persistence-configuration-unit, specifies the symbolic name of the object-to-datastore mapping to use.

When a child element of orm-file-jdor-mapping-factory, specifies the logical name of these mappings. Mapping files are suffixed with logicalname.orm. If not specified, the kodo.Mapping configuration property is used.

Example

<mapping>org/mag/Magazine-hsql.orm</mapping>

Function

Specifies the name of the column that holds the XML mapping.

Example

<mapping-column>MAPPING_DEF</mapping-column>

Function

Configures the mapping defaults if you set default-mapping-defaults to jdo.

Example

<mapping-defaults-impl>
    <use-class-criteria>false</use-class-criteria>
    <base-class-strategy>ColumnPerLockGroupVersionStrategy</base-class-strategy>
    <version-strategy>version-number</version-strategy>
    <discriminator-column-name>test</discriminator-column-name>
    <subclass-strategy>vertical</subclass-strategy>
    <index-version>false</index-version>
    <index-logical-foreign-keys>true</index-logical-foreign-keys>
    <null-indicator-column-name>null</null-indicator-column-name>
    <foreign-key-delete-action></foreign-key-delete-action>
    <join-foreign-key-delete-action>1</join-foreign-key-delete-action>
    <discriminator-strategy>final</discriminator-strategy>
    <defer-constraints>false</defer-constraints>
    <field-strategies>none</field-strategies>
    <version-column-name>version</version-column-name>
    <data-store-id-column-name>ID</data-store-id-column-name>
    <index-discriminator>true</index-discriminator>
    <store-enum-ordinal>false</store-enum-ordinal>
    <order-lists>true</order-lists>
    <order-column-name>false</order-column-name>
    <add-null-indicator>false</add-null-indicator>
    <store-unmapped-object-id-string>false</store-unmapped-object-id-string>
</mapping-defaults-impl>

Function

A plugin string describing the kodo.meta.MetaDataFactory to use to store and retrieve object-relational mapping information for your persistent classes. This setting is valid for JDO 1.0.

Example

<mapping-file-deprecated-jdo-mapping-factory>
    <use-schema-validation>true</use-schema-validation>
    <urls>t3://localhost:7001/metadata.jar</urls>
    <files>com/file1;com/file2</files>
    <classpath-scan>build</classpath-scan>
    <single-file>false</single-file>
    <types>classname1;classname2</types>
    <store-mode>1</store-mode>
    <strict></strict>
    <resources>com/aaa/package.jdo;com/bbb/package.jdo</resources>
    <scan-top-down>false</scan-top-down>
</mapping-file-deprecated-jdo-mapping-factory>

Function

Specifies the maximum allowed number of TCP sockets (channels) to open simultaneously between each peer in the cluster.

Example

<max-active>2</max-active>

Function

Specifies the maximum allowed number of TCP sockets (channels) to open simultaneously between each peer in the cluster.

Example

<max-idle>2</max-idle>

Function

Defines the maximum size of the concurrent hash map used to associate query strings and their parsed form.

Example

<max-size>2147483647</max-size>

Function

Flag that specifies whether to sort statements in order to optimize batch size when statement batching is on.

Example

<maximize-batch-size>true</maximize-batch-size>

Function

If JMX-based management is enabled, Kodo needs to locate an existing MBeanServer or create a new one, based on one of the following options:

• any-create—Locate an existing MBeanServer. If multiple are found, use the first one. If none are found, create a new server. This is the default.

• create—Create a new server. Do not attempt to find an existing MBeanServer.

• agentId:<agentID>—Locate an existing MBeanServer with the given agent id. If not found, create a new server.

Example

<MBeanServerStrategy>any-create</MBeanServerStrategy>

Function

Flag that specifies whether persistent instances and Kodo components are accessed by multiple threads at once.

Example

<multithreaded>false</multithreaded>

Function

Enable remote management via MX4J v.1.x implementations (supporting versions of the JMX specification prior to 1.2). Supports optional parameters in the Management Group and the Remote Group.

Example

<mx4j1-jmx>
    <MBeanServerStrategy>any-create</MBeanServerStrategy>
    <EnableLogMBean>true</EnableLogMBean>
    <EnableRuntimeMBean>true</EnableRuntimeMBean>
    <Host>localhost</Host>
    <Port>1099</Port>
    <JNDIName>jrmp</JNDIName>
</mx4j1-jmx>

Function

Configuration values for the MySQL Dictionary persistence plugin. For a complete description of each of the values that you can specify, see "MySQL Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

The mysql-dictionary element shares the same subelements as access-dictionary, plus the following subelements (defaults shown):

<mysql-dictionary>
...
   <table-type>innodb</table-type>
   <use-clobs>true</use-clobs>
   <driver-deserializes-blobs>true</driver-deserializes-blobs>
</mysql-dictionary>

Function

Specifies the name of the corresponding element.

Function

Name of the column that holds the mapping name. For class mappings, the mapping name is the class name. For named queries and sequences, it is the sequence or query name.

Example

<name-column>NAME</name-column>

Function

Classname of the naming service implementation to start in order to register the RMI connector with a JNDI name. Defaults to mx4j.tools.naming.NamingService, which is appropriate for MX4J v. 2.x. If set to the empty string, no naming service will be started. This setting is appropriate if a naming service is already running, or if a non-RMI connector is used.

Example

<NamingImpl>mx4j.tools.naming.NamingService</NamingImpl>

Function

Specifies a plugin string describing the kodo.kernel.Seq interface to use to create your own custom generators, in this case kodo.jdbc.kernel.NativeJDBCSeq.

Many databases have a concept of native sequences—a built-in mechanism for obtaining incrementing numbers. For example, in Oracle, you can create a database sequence with a statement like CREATE SEQUENCE MYSEQUENCE. Sequence values can then be atomically obtained and incremented with the statement SELECT MYSEQUENCE.NEXTVAL FROM DUAL. Kodo provides support for this common mechanism of sequence generation with the NativeJDBCSeq.

Example

<native-jdbc-seq>
    <type>0</type>
    <allocate>50</allocate>
    <table-name>DUAL</table-name>
    <initial-value>1</intial-value>
    <sequence>OPENJPA_SEQUENCE</sequence>
    <sequence-name>OPENJPA_SEQUENCE</sequence-name>
    <format>format</format>
    <increment>1</increment>
</native-jdbc-seq>

Function

No management is turned on. This is the default. For more information, see "Configuration" in Kodo JPA/JDO Reference for Oracle WebLogic Server.

Example

<none-jmx/>

Function

Specifies the kodo.kernel.NoneLockManager which does not perform any locking.

Example

<none-lock-manager/>

Function

Disable logging.

Example

<none-log-factory/>

Function

Specifies a plugin string describing the kodo.event.OrphanedKeyAction to invoke when Kodo discovers an orphaned datastore key, in this case kodo.event.NoneOrphanedKeyAction. In this case, Kodo ignores orphaned keys.

Example

<none-orphaned-key-action/>

Function

Turns off profiling of your code.

Example

<profiling>
  <none-profiling/>
</profiling>

Function

Flag that specifies whether the Kodo runtime allows you to read data outside of a transaction.

Example

<nontransactional-read>true</nontransactional-read>

Function

Flag that specifies whether the you can modify persistent objects and perform persistence operations outside of a transaction. Changes will take effect in the next transaction.

Example

<nontransactional-write>false</nontransactional-write>

Function

Specifies the number of threads to create for the purpose of transmitting events to peers. You should increase this value as the number of concurrent transactions increases. The maximum number of concurrent transactions is a function of the size of the connection pool. Setting a value of 0 will result in behavior where the thread invoking commit will perform the broadcast directly.

Example

<num-broadcast-threads>2<num-broadcast-threads>

Function

Defines an update manager that writes SQL in object-level operation order.

Example

<operation-order-update-manager/>

Function

Flag that specifies whether the datastore transactional mode is optimistic.

Example

<optimistic>true</optimistic>

Function

Configuration values for the Oracle Dictionary persistence plugin. For a complete description of each of the values that you can specify, see "Oracle Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

The oracle-dictionary element shares the same subelements as access-dictionary, plus the following subelements (defaults shown):

<oracle-dictionary>
...
   <use-triggers-for-auto-assign>false</use-triggers-for-auto-assign>
   <auto-assign-sequence-name>false</auto-assign-sequence-name>
   <use-set-form-of-use-for-unicode>true</use-set-form-of-use-for-unicode>
</oracle-dictionary>

Function

Specifies a plugin string describing the kodo.kernel.SavepointManager to use for managing transaction savepoints, in this case the default which is kodo.jdbc.sql.OracleSavepointManager. This plugin operates similarly to jdbc3-savepoint-manager, but it uses Oracle-specific calls. This plugin requires using the Oracle JDBC driver and database, versions 9.2 or higher. This plugin implements savepoints by issuing a flush to the database.

Example

<oracle-savepoint-manager/>

Function

A plugin string describing the kodo.jdo.jdbc.ORMFileJDORMappingFactory that stores mapping metadata in.orm files. This setting is valid for JDO 1.0.

Example

<orm-file-jdor-mapping-factory>
    <use-schema-validation>true</use-schema-validation>
    <mapping>mapping</mapping>
    <urls>t3://localhost:7001/metadata.jar</urls>
    <files>com/file1;com/file2</files>
    <classpath-scan>build</classpath-scan>
    <types>classname1;classname2</types>
    <store-mode>1</store-mode>
    <strict>false</strict>
    <resources>com/aaa/package.jdo;com/bbb/package.jdo</resources>
    <scan-top-down>false</scan-top-down>
</orm-file-jdor-mapping-factory>

Function

Flag that specifies whether Kodo maintains the order that changes were made to dirty objects when writing the changes back to the database.

Example

<order-dirty-objects>false</order-dirty-objects>

Function

Password that Kodo should use to access the WebLogic MBeanServer. This must be set.

Example

<Password>admin</Password>

Function

Root element of the persistence deployment descriptor.

Function

Contains the deployment information for a persistence unit that is available in WebLogic Server.

Function

Specifies the kodo.jdbc.kernel.PessimisticLockManager, which uses SELECT FOR UPDATE statements (or the database's equivalent) to lock the database rows corresponding to locked objects. This lock manager does not distinguish between read locks and write locks; all locks are write locks.

Example

<pessimistic-lock-manager>
    <version-check-on-read-lock>false</version-check-on-read-lock>
    <version-update-on-write-lock>false</version-update-on-write-lock>
</pessimistic-lock-manager>

Function

Configures the mapping defaults if you set default-mapping-defaults to jpa.

Example

The persistence-mapping-defaults element shares the same subelements as mapping-defaults-impl.

Function

Flag that specifies whether to populate the data cache. If your transaction will visit objects that you know are very unlikely to be accessed by other transactions, for example an exhaustive report run only once a month, you can turn off population of the data cache so that the transaction does not fill the entire data cache with objects that will not be accessed again.

Example

<populate-data-cache>true</populate-data-cache>

Function

Port on which the RMI registry naming service listens. Defaults to 1099.

Example

<Port>1099</Port>

Function

Specifies the port on which the server will listen. This setting is used by clients, not by the server.

If the parent element is tcp-transport, the element defaults to 5637.

If the parent element is tcp-remote-commit-provider, the element defaults to 5636.

Example

<port>5637</port>

Function

Configuration values for the Postgres Dictionary persistence plugin. For a complete description of each of the values that you can specify, see "Postgres Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

The postgres-dictionary element shares the same subelements as access-dictionary, plus the following subelements (defaults shown):

<postgres-dictionary>
...
   <all-sequences-sql>SELECT NULL AS SEQUENCE_SCHEMA, relname AS SEQUENCE_NAME FROM pg_class WHERE relkind='S'</all-sequence-sql>
   <named-sequences-from-all-schemas-sql>SELECT NULL AS SEQUENCE_SCHEMA, relname AS SEQUENCE_NAME FROM pg_class WHERE relkind='S' AND relname = ?"</named-sequences-from-all-schemas-sql>
   <all-sequences-from-one-schema-sql>SELECT NULL AS SEQUENCE_SCHEMA, relname AS SEQUENCE_NAME FROM pg_class, pg_namespace WHERE relkind='S' AND pg_class.relnamespace = pg_namespace.oid AND nspname = ?</all-sequences-from-one-schema-sql>
   <named-sequences-from-one-schema-sql>SELECT NULL AS SEQUENCE_SCHEMA, relname AS SEQUENCE_NAME FROM pg_class, pg_namespace WHERE relkind='S' AND pg_class.relnamespace = ?</named-sequences-from-one-schema-sql>
   <supports-set-fetch-size>true</supports-set-fetch-size>
</postgres-dictionary>

Function

Specifies the name of the table's numeric primary key column.

Example

<primary-key-column>ID</primary-key-column>

Function

Specifies the primary key that is used by this instance.

Example

<primary-key-value>DEFAULT</primary-key-value>

Function

Flag that specifies whether to read automatically primary key information during schema validation.

Example

<primary-keys>false</primary-keys>

Function

Enables you to configure profiling of your application code.

Example

<profiling>
    <export-profiling>
        <interval-millis>-1</interval-millis>
        <base-name>name</base-name>
    </export-profiling>
</profiling>
<profiling>
    <gui-profiling/>
</profiling>
<profiling>
    <local-profiling/>
</profiling>
<profiling>
    <none-profiling/>
</profiling>

Function

Configures the profiling proxy manager.

Example

<profiling-proxy-manager>
    <assert-allowed-type>false</assert-allowed-type>
    <track-changes>true</track-changes>
</profiling-proxy-manager>

Function

Specifies one or more property elements.

Function

Enables you to specify the name and value of a property.

Example

<property>
   <name>timeout</name>
   <value>1000</value>
</property>

Function

Configures the default proxy manager.

Example

<proxy-manager-impl>
    <assert-allowed-type>false</assert-allowed-type>
    <track-changes>true</track-changes>
</proxy-manager-impl>

Function

A plugin string describing the kodo.datacache.QueryCache implementation to use for caching of queries loaded from the data store.

Example

<query-caches>
    <default-query-cache>...</default-query-cache>
</query-caches>
<query-caches>
    <kodo-concurrent-query-cache>...</kodo-concurrent-query-cache>
</query-caches>
<query-caches>
    <gem-fire-query-cache>...</gem-fire-query-cache>
</query-caches>
<query-caches>
    <lru-query-cache>...</lru-query-cache>
</query-caches>
<query-caches>
    <tangosol-query-cache>...</tangosol-query-cache>
</query-caches>
<query-caches>
    <disabled-query-cache>...</disabled-query-cache>
</query-caches>
<query-caches>
    <custom-query-cache>...</custom-query-cache>
</query-caches>

Function

Flag that specifies whether to interpret quoted numbers in query strings as numbers, as opposed to strings. Set to true to mimic the behavior of Kodo 3.1 and earlier and treat quoted numbers as numbers.

Example

<quoted-numbers-in-queries>false</quoted-numbers-in-queries>

Function

Sets the default read level at which to lock objects retrieved during a non-optimistic transaction. Valid values include:

• none—No lock level.

• read—Read lock level.

• write—Write lock level.

• Numeric values for lock-manager specific lock levels.

  Note:

  For the default JDBC lock manager, the read and write lock levels are equivalent.

Example

<read-lock-level>read</read-lock-level>

Function

Specifies the action to take during recovery. Valid values include:

• none—No action is performed.

• clear—Clears the notifications.

Example

<recover-action>none</recover-action>

Function

Specifies the amount of time to wait in milliseconds before attempting to reconnect to a peer of the cluster when connectivity to the peer is lost.

Example

<recovery-time-millis>15000</recovery-time-millis>

Function

Specifies a semicolon-separated list of resource paths to metadata files or jar archives. Each jar archive will be scanned for annotated JPA entities or JDO metadata files based on your metadata factory.

Example

<resources>com/aaa/package.jdo;com/bbb/package.jdo</resources>

Function

Flag that specifies whether to restore managed fields to their pre-transaction values when a rollback occurs.

Valid values include:

• all (1)—Restores all managed values.

• none (2)—Do not roll back state. The object becomes hollow and will reload its state the next time it is accessed.

• immutable (3)—Restores immutable values (primitives, primitive wrappers, strings) and clears mutable values so that they are reloaded on next access.

• true (4)—Same as all.

• false (5)—Same as none.

Example

<restore-state>none</restore-state>

Function

Specifies the JDBC result set type to use when fetching return lists. This setting can also be varied at runtime.

Valid values include:

• forward-only—Result set whose cursor may move only forward. The result set is not updatable.

• scroll-sensitive—Scrollable result set that is sensitive to changes made by others. The result set is updatable.

• scroll-insensitive—Scrollable result set that is not sensitive to changes made by others. The result set is updatable.

Example

<result-set-type>forward-only</result-set-type>

Function

Flag that specifies whether persistent fields retain their values on transaction commit. This element defaults to true when a child element of the persistence-configuration-unit and false when a child element of the kodo-broker element.

Example

<retain-state>true</retain-state>

Function

Flag that specifies whether to log a warning and defer registration instead of throwing an exception when a persistent class cannot be fully processed. This element should only be used in complex classloader situations where security is preventing Kodo from reading registered classes. Setting this to true unnecessarily may obscure more serious problems.

Example

<retry-class-registration>false</retry-class-registration>

Function

Flag that specifies whether to search for metadata files top-down in the package tree. Kodo defaults to bottom-up scanning. For example, when scanning metadata for class C, Kodo looks first for C.jdo, then package.jdo in C's package, then package.jdo in the parent package, and so on to the package root. For more information, see "Metadata Factory" in Kodo JPA/JDO Reference for Oracle WebLogic Server.

Example

<scan-top-down>false</scan-top-down>

Function

Specifies the default schema name to prepend to unqualified table names. In addition, specifies the schema in which Kodo creates new tables. For more information, see "Default Schema" in the Kodo JPA/JDO Reference for Oracle WebLogic Server.

Example

<schema>SCHEMA</schema>

Function

Specifies the name of the table's string column for holding the schema definition as an XML string.

Example

<schema-column>SCHEMA_DEF</schema-column>

Function

Specifies a comma-separated list of the schemas and/or tables used for your persistent data.

Example

<schemas>BUSOBJS,GENERAL.ADDRESS,.SYSTEM_INFO </schemas>

Function

Specifies the name of the database sequence.

Example

<sequence>OPENJPA_SEQUENCE</sequence>

Function

Specifies the name of the column that holds the current sequence value.

Example

<sequence-column>SEQUENCE_VALUE</sequence-column>

Function

Specifies the name of the database sequence.

Example

<sequence-name>OPENJPA_SEQUENCE</sequence-name>

Function

JMX service URL name under which to register the JMX Connector Server. This value defaults to service:jmx:rmi://localhost/jndi/jmxservice, indicating that the RMI connector will be used and registered under the JNDI name jmxsevice.

Example

<ServiceURL>service:jmx:rmi://localhost/jndi/jmxservice</ServiceURL>

Function

Configures the Kodo datasource implementation.

Example

<simple-driver-data-source>
    <connection-user-name>user</connection-user-name>
    <login-timeout>10</login-timeout>
    <connection-password>password</connection-password>
    <connection-url>jdbc:hsqldb:db-hypersonic</connection-url>
    <connection-driver-name>org.hsqldb.jdbcDrier</connection-driver-name>
</simple-driver-data-source>

Function

Flag specifying whether or not to use a single file.

Example

<single-file>false</single-file>

Function

Specifies the kodo.kernel.SingleJVMExclusiveLockManager. This lock manager uses in-memory mutexes to obtain exclusive locks on object ids. It does not perform any database-level locking. Also, it does not distinguish between read and write locks; all locks are write locks.

Example

<single-jvm-exclusive-lock-manager>
    <version-check-on-read-lock>false</version-check-on-read-lock>
    <version-check-on-write-lock>false</version-check-on-write-lock>
</single-jvm-exclusive-lock-manager>

Function

Configures Kodo to share commit notifications among persistenceManagerFactories in the same JVM.

Example

<single-jvm-remote-commit-provider>
    <name>kodo.RemoteCommitProvider</name>
</single-jvm-remote-commit-provider>

Function

Sets the number of soft references that Kodo maintains. When the maximum cache or query size is reached, random entries are moved to a soft reference map so that they are maintained for awhile longer. By default, this value is set to -1 which specifies that an unlimited number of soft references are maintained. Set the property to 0 to disable soft references.

Example

<soft-reference-size>-1</soft-reference-size>

Function

Specifies the socket read timeout in milliseconds.

Example

<so-timeout>0</so-timeout>

Function

Configuration values for the SQLServer Dictionary persistence plugin. For a complete description of each of the values that you can specify, see "SQLServer Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

The sql-server-dictionary element shares the same subelements as access-dictionary, plus the following subelements (defaults shown):

<sql-server-dictionary>
...
   <unique-identifier-as-varbinary>true</unique-identifier-as-varbinary>
</sql-server-dictionary>

Function

Provider examines the current thread's stack and builds an execution context name based on that information.

Example

<stack-execution-context-name-provider> 
    <style>full</style>
</stack-execution-context-name-provider>

Function

Specifies the data store mode.

Example

<store-mode>1</store-mode>

Function

Flag that specifies whether strict mode is enabled.

Example

<strict>true</strict>

Function

Flag that specifies whether to require identity values used for finding application identity instances to be of the exact right type. By default, Kodo allows stringified identity values, and performs conversions between numeric types.

Example

<strict-identity-values>false</strict-identity-values>

Function

Provider examines the current thread's stack and builds an execution context name based on that information and the following setting:

• line—Name will be the first non-Kodo stack line, including class name, method name, and line number, if available.

• partial—Full stack trace minus the Kodo lines will be used.

• full—Entire stack trace will be used.

Example

<style>full</style>

Function

Specifies the method to use to select subclass data when it is in other tables. For a description of the valid values, see under eager-fetch-mode.

Example

<subclass-fetch-mode>join</subclass-fetch-mode>

Function

Configuration values for the Sybase Dictionary persistence plugin. For a complete description of each of the values that you can specify, see "Sybase Dictionary Configuration" in the Oracle WebLogic Server Administration Console Online Help.

Example

The sybase-dictionary element shares the same subelements as access-dictionary, plus the following subelements (defaults shown):

<sybase-dictionary>
...
   <create-identity-column>true</create-identity-column>
   <identity-column-name>UNQ_INDEX</identity-column-name>
</sybase-dictionary>

Function

Flag that specifies whether to sync with managed transactions.

Example

<sync-with-managed-transactions>false</sync-with-managed-transactions>

Function

Controls whether Kodo attempts to run the mapping tool on all persistent classes to synchronize their mappings and schema at runtime. This element save you the trouble of running the mapping tool manually, and is useful for rapid test and debug cycles.

Example

<synchronize-mappings>false</synchronize-mappings>

Function

Specifies the name of the table. The default value depends on the parent element:

• class-table-jdbc-seq: OPENJPA_SEQUENCE_TABLE

• table-jdbc-seq: OPENJPA_SEQUENCE_TABLE

• table-jdor-mapping-factory: KODO_JDO_MAPPINGS

• table-schema-factory: OPENJPA_SCHEMA

• value-table-jdbc-seq: OPENJPA_SEQUENCES_TABLE

Example

<table>KODO_JDO_MAPPING</table>

Function

A plugin string describing the kodo.jdo.jdbc.TableJDORMappingFactory that stores mapping metadata as XML strings in a database table. This setting is valid for JDO 1.0.

Example

<table-deprecated-jdo-mapping-factory>
    <table-name>JDO_MAPPING</table-name>
    <urls>t3://localhost:7001/metadata.jar</urls>
    <classpath-scan>build</classpath-scan>
    <types>classname1;classname2</types>
    <mapping-column>MAPPING_DEF</mapping-column>
    <store-mode></store-mode>
    <strict>false</strict>
    <name-column>NAME</name-column>
    <use-schema-validation>false</use-schema-validation>
    <single-row>false</single-row>
    <files>com/file1;com/file2</files>
    <scan-top-down>false</scan-top-down>
    <resources>com/aaa/package.jdo;com/bbb/package.jdo</resources>
</table-deprecated-jdo-mapping-factory>

Function

Specifies a plugin string describing the kodo.kernel.Seq interface to use to create your own custom generators, in this case kodo.jdbc.kernel.TableJDBCSeq.

The TableJDBCSeq uses a special single-row table to store a global sequence number. If the table does not already exist, it is created the first time you run the mapping tool's on a class that requires it. You can also use the class' main method or the sequencetable shell/bat script to manipulate the table; see the TableJDBCSeq.main method Javadoc for usage details.

Example

<table-jdbc-seq>
    <type>0</type>
    <allocate>50</allocate>
    <table-name>OPENJPA_SEQUENCE_TABLE</table-name>
    <table>OPENJPA_SEQUENCE_TABLE</table>
    <primary-key-column>ID</primary-key-column>
    <sequence-column>SEQUENCE_VALUE</sequence-column>
    <increment>1</increment>
</table-jdbc-seq>

Function

A plugin string describing the kodo.jdo.jdbc.TableJDORMappingFactory that stores mapping metadata as XML strings in a database table. This setting is valid for JDO 2.0.

Example

<table-jdor-mapping-factory>
    <use-schema-validation>false</use-schema-validation>
    <type-column>0</type-column>
    <constraint-names>false</constraint-names>
    <table>KODO_JDO_MAPPINGS</table>
    <types>classname1;classname2</types>
    <store-mode></store-mode>
    <mapping-column>false</mapping-column>
    <strict>false</strict>
    <name-column>NAME</name-column>
</table-jdor-mapping-factory>

Function

Defines an update manager capable of statement batching, that ignores foreign keys and auto-increment, but optimizes for table level locking. This is useful when using table-level locking and trying to avoid deadlocks.

Example

<table-lock-update-manager>
    <maximize-batch-size>true</maximize-batch-size>
</table-lock-update-manager>

Function

Specifies the name of the table.

The default varies based on the parent element, as follows:

• class-table-jdbc-seq: OPENJPA_SEQUENCES_TABLE.

• native-jdbc-seq: DUAL.

• table-deprecated-jdo-mapping-factory: JDO_MAPPING.

• table-jdbc-seq: OPENJPA_SEQUENCE_TABLE.

• table-schema-factory: OPENJPA_SCHEMA.

• value-table-jdbc-seq: OPENJPA_SEQUENCE_TABLE.

Example

<table-name>JDO_MAPPING</table-name>

Function

Specifies a plugin string describing the kodo.jdbc.schema.SchemaFactory to use to store and retrieve information about the database schema, in this case kodo.jdbc.schema.TableSchemaFactory.

This schema factory stores schema information as an XML document in a database table it creates for this purpose. If your JDBC driver doesn't support the java.sql.DatabaseMetaData standard interface, but you still want some schema validation to occur at runtime, you might use this factory. It is not recommended for most users, though, because it is easy for the stored XML schema definition to get out-of-sync with the actual database.

Example

<table-schema-factory>
    <schema-column>SCHEMA_DEF</schema-column
    <table-name>OPENJPA_SCHEMA</table-name>
    <table>OPENJPA_SCHEMA</table>
    <primary-key-column>ID</primary-key-column>
</table-schema-factory>

Function

Name of the Tangosol Coherence cache to use.

Example

<tangosol-cache-name>kodo</tangosol-cache-name>

Function

Type of Tangosol Coherence cache to use. Valid values include:

• named—Cache is looked up via the com.tangosol.net.CacheFactory.getCache(String) method. This method looks up the cache by the name as defined in the Coherence configuration.

• distributed

• replicated

Example

<tangosol-cache-type>name</tangosol-cache-type>

Function

Integrates with Tangosol's Coherence caching system.

Example

<data-caches>
    <tangosol-data-cache>
        <name>kodo.dataCache</name>
        <clear-on-close>false</clear-on-close>
        <tangosol-cache-type>name</tangosol-cache-type>
        <tangosol-cache-name>kodo</tangosol-cache-name>
        <eviction-schedule>15,45 15 * * 1</eviction-schedule>
    </tangosol-data-cache>
</data-caches>

Function

Configures the TCP remote commit provider.

Example

<tcp-remote-commit-provider>
    <name>kodo.RemoteCommitProvider</name>
    <max-idle>2</max-idle>
    <num-broadcast-threads>2<num-broadcast-threads>
    <recovery-time-millis>15000</recovery-time-millis>
    <max-active>2</max-active>
    <port>5636</port>
    <addresses>[]</addresses>
</tcp-remote-commit-provider>

Function

Specifies the transport layer for the remote communication.

Example

<tcp-transport>
    <so-timeout>0</so-timeout>
    <host>localhost</host>
    <port>5637</port>
</tcp-transport>

Function

Specifies a plugin string describing the kodo.kernel.Seq interface to use to create your own custom generators, in this case kodo.jdbc.kernel.TimeSeededSeq.

This type uses an in-memory static counter, initialized to the current time in milliseconds and monotonically incremented for each value requested. It is only suitable for single-JVM environments.

Example

<time-seeded-seq>
    <type>0</type>
    <increment>1</increment>
</time-seeded-seq>

Function

Specifies the topic to which the remote commit provider should publish notifications and subscribe for notifications sent from other JVMs.

Example

<topic>topic/KodoCommitProviderTopic</topic>

Function

Specifies the JNDI name of a javax.jms.TopicConnectionFactory factory to use for finding topics. This setting may vary depending on the application server in use; consult the application server's documentation for details about the default JNDI name for the topic instance. For WebLogic, the JNDI name for the TopicConnectionFactory is javax.jms.TopicConnectionFactory.

Example

<topic-connection-factory>java:/ConnectionFactory</topic-connection-factory>

Function

Flag that specifies whether to use smart proxies.

Example

<track-changes>true</track-changes>

Function

Specifies the JDBC transaction isolation level to use.

• default—JDBC driver's default level. This is the default.

• none—No transaction isolation.

• read-committed—Dirty reads are prevented; non-repeatable reads and phantom reads can occur.

• read-uncommitted—Dirty reads, non-reputable reads, and phantom reads can occur.

• repeatable-read—Dirty reads and non-repeatable reads are prevented; phantom reads can occur.

• serializable—Dirty reads, non-reputable reads, and phantom reads are prevented.

Example

<transaction-isolation>default</transaction-isolation>

Function

Specifies the transaction mode to use. You can override this setting per session.

• local—Perform transaction operations locally. This is the default.

• managed—Integrate with the application server's managed global transactions.

Example

<transaction-mode>local</transaction-mode>

Function

Provider returns the current transaction's name, as defined by WebLogic transaction naming semantics.

Example

<transacation-name-execution-context-name-provider/>

Function

Specifies the type of generator.

Example

<type>0</type>

Function

Specifies the name of the column that holds the mapping type. Valid types constants include:

• 0—Class mapping.

• 1—Named sequence.

• 2—System-level named query.

• 3—Class-level named query.

Example

<type-column>0</type-column>

Function

Specifies a semicolon-separated list of fully-qualified persistent class names.

Example

<types>classname1; classname2</types>

Function

URL to which Kodo should connect to access the WebLogic MBeanServer.

Example

<URL>t3://localhost:7001</URL>

Function

URL to which Kodo should connect to access the remote server.

Example

<url>t3://localhost:7001/remote-server</url>

Function

Specifies a semicolon-separated list of URLs of metadata files or jar archives. Each jar archive will be scanned for annotated JPA entities or JDO metadata files based on your metadata factory.

Example

<urls>t3://localhost:7001/metadata.jar</urls>

Function

Flag that specifies whether to use each class' entity name as the primary key value of each row rather than the full classname.

Example

<use-aliases>false</use-aliases>

Function

Flag that specifies whether to use schema validation.

Example

<use-schema-validation>true</use-schema-validation>

Function

Provider returns the user object specified in the current EntityManager/PersistenceManager whose key is com.solarmetric.profile.ExecutionContextNameProvider. User objects can be set using the OpenJPAEntityManager.putUserObject(Object,Object) or PersistenceManager.putUserObject(Object,Object).

Example

<user-object-execution-context-name-provider/>

Function

Specifies the username that Kodo should use to access the WebLogic MBeanServer. This must be set.

Example

<wls81-jmx>
    <MBeanServerStrategy>any-create</MBeanServerStrategy>
    <EnableLogMBean>true</EnableLogMBean>
    <EnableRuntimeMBean>true</EnableRuntimeMBean>
    <URL>t3://localhost:7001</URL>
    <UserName>admin</UserName>
    <Password>admin</Password>
</wls81-jmx>

Function

Flag that specifies whether to return hollow objects (objects for which no state has been loaded) from calls to PersistenceManager.getObjectById(oid, false). This is the default behavior of Kodo 4.0 and above. Previous Kodo versions, however, always loaded the object from the datastore. Set this property to false to get the old behavior.

Example

<validate-false-returns-hollow>true</validate-false-returns-hollow>

Function

Flag that specifies whether to check the datastore to be sure the given oid exists. Prior to Kodo 4.0, calling PersistenceManager.getObjectById(oid, true) always checked the datastore to be sure the given oid existed, even when the corresponding object was already cached. Kodo 4.0 and above does not check the datastore when the instance is already cached and loaded. Set this property to true to mimic previous behavior.

Example

<validate-true-checks-store>false</validate-true-checks-store>

Function

Specifies a plugin string describing the kodo.kernel.Seq interface to use to create your own custom generators, in this case kodo.jdbc.kernel.ValueTableJDBCSeq.

This Seq is like the table-jdbc-seq, but has an arbitrary number of rows for sequence values, rather than a fixed pattern of one row per class.

Example

<value-table-jdbc-seq>
    <type>0</type>
    <allocate>50</allocate>
    <table-name>OPENJPA_SEQUENCE_TABLE</table-name>
    <primary-key-value>DEFAULT</primary-key-value>
    <table>OPENJPA_SEQUENCE_TABLE</table>
    <primary-key-column>ID</primary-key-column>
    <sequence-column>SEQUENCE_VALUE</sequence-column>
    <increment>1</increment>
</value-table-jdbc-seq>

Function

Specifies whether to perform version checking and incrementing behavior of the pessimistic lock manager on read operations.

Example

<version-check-on-read-lock>false</version-check-on-read-lock>

Function

Specifies whether to perform version checking and incrementing behavior of the pessimistic lock manager on write operations.

Example

<version-check-on-write-lock>false</version-check-on-write-lock>

Function

Specifies the kodo.kernel.VersionLockManager. This lock manager does not perform any exclusive locking, but instead ensures read consistency by verifying that the version of all read-locked instances is unchanged at the end of the transaction. Furthermore, a write lock will force an increment to the version at the end of the transaction, even if the object is not otherwise modified. This ensures read consistency with non-blocking behavior.

Example

<version-lock-manager>
    <version-check-on-read-lock>false</version-check-on-read-lock>
    <version-check-on-write-lock>false</version-check-on-write-lock>
</version-lock-manager>

Function

Enable management and invoke the JMX management console in the local JVM. Supports optional parameters in the Management Group and WebLogic 8.1 Group.

Example

<wls81-jmx>
    <MBeanServerStrategy>any-create</MBeanServerStrategy>
    <EnableLogMBean>true</EnableLogMBean>
    <EnableRuntimeMBean>true</EnableRuntimeMBean>
    <URL>t3://localhost:7001</URL>
    <UserName>admin</UserName>
    <Password>admin</Password>
</wls81-jmx>

Function

Sets the default write level at which to lock objects retrieved during a non-optimistic transaction. Valid values include:

• none—No lock level.

• read—Read lock level.

• write—Write lock level.

• Numeric values for lock-manager specific lock levels.

  Note:

  For the default JDBC lock manager, the read and write lock levels are equivalent.

Example

<write-lock-level>read</write-lock-level>