NonStop Server for Java (NSJ) Programmer's Guide (NSJ 2.1+)

API-TMF; the version of NonStop Java Transaction API that uses JTS is called NonStop Java
Transaction API-JTS. NonStop Java Transaction API-TMF and NonStop Java Transaction API-JTS
have identical interfaces. You can specify TMF or JTS when you use
JTAFactory.getUserTransaction to get a reference to
javax.transaction.UserTransaction. (See examples.) The default is TMF.
NonStop Java Transaction API-TMF is intended for applications other than CORBA applications.
NonStop Java Transaction API-JTA is intended for CORBA applications. If you use NonStop Java
Transaction API-JTS for non-CORBA applications, results are unpredictable.
This subsection explains the following subjects:
javax.transaction interfaces
javax.transaction exceptions
Examples
For more information about JTA, see the Sun Microsystems JTA document
(http://www.javasoft.com/products/jta/index.html).
javax.transaction Interfaces
The Sun Microsystems JTA package, javax.transaction, defines the following interfaces:
Status
Synchronization
Transaction
TransactionManager
UserTransaction
NonStop Java Transaction API supports all of the preceding interfaces, but only
UserTransaction is available to client programs.
UserTransaction allows the client to control transaction boundaries programmatically.
UserTransaction methods do the following:
Begin transaction
Commit transaction
Obtain transaction status
Mark transaction for rollback
Rollback transaction
Set timeout for transaction
javax.transaction Exceptions
The Sun Microsystems JTA package, javax.transaction, defines the following exceptions.
NonStop Java Transaction API supports all of them.