CORBA 2.3.3 Programmer's Guide for Java

Chapter 7. Managing Transactions

Table of Contents

Components of Transaction Service Implementation

Use of TMF

Transaction Service Features Not Supported in NonStop CORBA

TransactionalObject Interface

Checked Transaction Behavior

Transaction Branches and the Diamond Access Problem

This section describes the NonStop CORBA implementation of the Transaction Service (formerly known

as the Object Transaction Service, or OTS) and explains programming considerations for transactions

in NonStop CORBA applications.

The Transaction Service components of NonStop CORBA for Java applications are referred to

collectively as NSJTS. Together, they implement the CosTransactions module of the Transaction

Service to provide distributed transactional execution. These components also implement the low-level

Java mapping of the OTS as defined in the Java Transaction Service (JTS) specification, version 1.0,

from Sun Microsystems, Inc.

The JTS_Bank sample is a set of programs that illustrate the use of NSJTS. The Readme file for this

sample provides a description and walkthrough of these programs, including how to build and run them.

Components of Transaction Service

Implementation

NSJTS consists of the following components:

JTS, a special client stub that implements the JTS API●

NSotsTM, a process that collaborates with the Transaction Management Facility (TMF) on the

NonStop Himalaya system to manage transactions and that can run as a TS/MP server pool

●

NSotsXID, a singleton process used to broker transaction identifiers (XIDs) when NSotsTM runs

as a TS/MP server pool with multiple processes

●