The Oracle JDBC Thin driver version 8.1.7 can be used for
JTA (Java Transaction API) with the following restrictions:
1. The thin driver that comes shipped with 8.1.7 may or may not work.
Future patches from Oracle may work as well, but have not been tested. The
driver that was available from the Oracle Technology Network web site as
of February 20, 2001 does work and is the recommended driver. Later
versions on this web site are expected to work as well but have not been
tested. To obtain the driver from the Oracle support web go to:
http://technet.oracle.com/
You will need to be a registered user for the Oracle Technology Network to
get the driver from this site. Contact Oracle for how to get access.
On the left hand side of the screen, select "Software".
On "Download Oracle Products, Drivers, and Utilities", on the "Select a
Utility or Driver" selection, pick "Oracle JDBC Drivers".
Download the 8.1.7 driver for the platforms you use and follow the
instructions for installing
the new driver.
2. The 8.1.7 driver must be used with 8.1.7 databases. 8.1.6 databases do
not support the recover() and forget() methods and other problems haven
been encountered running with 8.1.6. Oracle does not support JTA with
8.1.6.
3. For Oracle, JTA can only be used with container managed beans.
4. In order for the bean to create the table, the bean must first be
started the JTA set to false. After the bean has created the table, JTA
can be set back to true.
5. An entity bean that accesses Oracle with JTA set to true must be
configured as follows:
In the deployment descriptor properties,
Under Transactions, under the Remote tab, set the Transaction Attribute to
TX_REQUIRED.
Under Isolation, under the Remote tab, set the Isolation Level to
TRANSACTION_READ_COMMITTED.
6. A session bean that is used with an entity bean that accesses Oracle
with JTA set to true must be configured as follows:
In the deployment descriptor properties,
Under Transactions, under the Remote tab, set the Transaction Attribute to
TX_BEAN_MANAGED.
Under Isolation, under the Remote tab, set the Isolation Level to
TRANSACTION_READ_COMMITTED.
|