org.springframework.transaction.jta Documentation Differences

This file contains all the changes in documentation in the package org.springframework.transaction.jta as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Special JtaTransactionManager variant for Oracle OC4J (10.1.3 and higher). Supports the full power of Spring's transaction definitions on OC4J's transaction coordinator, beyond standard JTA: transaction names and per-transaction isolation levels.

Uses OC4J's special begin(name) method to start a JTA transaction, in orderto make Spring-driven transactions visible in OC4J's transaction monitor. In case of Spring's declarative transactions, the exposed name will (by default) be the fully-qualified class name + "." + method name.

Supports a per-transaction isolation level through OC4J's corresponding OC4JTransaction.setTransactionIsolation(int) method. This will apply the specified isolation level (e.g. ISOLATION_SERIALIZABLE) to all JDBC Connections that participate in the given transaction.

Automatically detects the available OC4J server version and adapts accordingly. Supports the "com.evermind.server" package in OC4J 10.1.3.2 as well as the "oracle.j2ee.transaction" package in later OC4J versions.

By default, the JTA UserTransaction and TransactionManager handles are fetched directly from OC4J's TransactionUtility in 10.1.3.2+. This can be overridden by specifying "userTransaction"/"userTransactionName" and "transactionManager"/"transactionManagerName", passing in existing handles or specifying corresponding JNDI locations to look up.

Thanks to Oracle for donating the original version of this extended OC4J integration code to the Spring project! @author Paul Parkinson @author Juergen Hoeller @since 2.0.3 @see org.springframework.transaction.TransactionDefinition#getName @see org.springframework.transaction.TransactionDefinition#getIsolationLevel @see oracle.j2ee.transaction.OC4JTransactionManager#begin(String) @see oracle.j2ee.transaction.OC4JTransaction#setTransactionIsolation @see oracle.j2ee.transaction.TransactionUtilityTransactionUtility @deprecated as of Spring 3.2, in favor of WebLogicJtaTransactionManager since Oracle end-of-lifed OC4J in favor of WebLogic