Exit Print View

Sun GlassFish Enterprise Server v3 Application Development Guide

  This Document Entire Library
Print View

Document Information

Preface

Part I Development Tasks and Tools

1.  Setting Up a Development Environment

2.  Class Loaders

3.  Using Ant with Enterprise Server

4.  Debugging Applications

Part II Developing Applications and Application Components

5.  Securing Applications

6.  Developing Web Services

7.  Using the Java Persistence API

8.  Developing Web Applications

9.  Using Enterprise JavaBeans Technology

10.  Using Container-Managed Persistence

11.  Developing Java Clients

12.  Developing Connectors

13.  Developing Lifecycle Listeners

Part III Using Services and APIs

14.  Using the JDBC API for Database Access

15.  Using the Transaction Service

16.  Using the Java Naming and Directory Interface

17.  Using the Java Message Service

The JMS Provider

Message Queue Resource Adapter

Generic Resource Adapter

Administration of the JMS Service

Configuring the JMS Service

The Default JMS Host

Creating JMS Hosts

Checking Whether the JMS Provider Is Running

Creating Physical Destinations

Creating JMS Resources: Destinations and Connection Factories

Restarting the JMS Client After JMS Configuration

JMS Connection Features

Connection Pooling

Connection Failover

Transactions and Non-Persistent Messages

Using the ConfigurableTransactionSupport Interface

Authentication With ConnectionFactory

Message Queue varhome Directory

Delivering SOAP Messages Using the JMS API

To Send SOAP Messages Using the JMS API

To Receive SOAP Messages Using the JMS API

18.  Using the JavaMail API

Index

Using the ConfigurableTransactionSupport Interface

The Java EE Connector 1.6 specification allows a resource adapter to use the transaction-support attribute to specify the level of transaction support that the resource adapter handles. However, the resource adapter vendor does not have a mechanism to figure out the current transactional context in which a ManagedConnectionFactory is used.

If a ManagedConnectionFactory implements an optional interface called com.sun.appserv.connectors.spi.ConfigurableTransactionSupport, the Enterprise Server notifies the ManagedConnectionFactory of the transaction-support configured for the connector connection pool when the ManagedConnectionFactory instance is created for the pool. Connections obtained from the pool can then be used with a transaction level at or lower than the configured value. For example, a connection obtained from a pool that is set to XA_TRANSACTION could be used as a LOCAL resource in a last-agent-optimized transaction or in a non-transactional context.