JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.1 Application Development Guide
search filter icon
search icon

Document Information


Part I Development Tasks and Tools

1.  Setting Up a Development Environment

2.  Class Loaders

3.  Debugging Applications

Part II Developing Applications and Application Components

4.  Securing Applications

5.  Developing Web Services

6.  Using the Java Persistence API

7.  Developing Web Applications

8.  Using Enterprise JavaBeans Technology

9.  Using Container-Managed Persistence

10.  Developing Java Clients

11.  Developing Connectors

Connector Support in the GlassFish Server

Connector Architecture for JMS and JDBC

Connector Configuration

Advanced Connector Configuration Options

Thread Associations

Security Maps

Work Security Maps

Overriding Configuration Properties

Testing a Connector Connection Pool

Flushing a Connector Connection Pool

Handling Invalid Connections

Setting the Shutdown Timeout

Specifying the Class Loading Policy

Using Last Agent Optimization of Transactions

Disabling Pooling for a Connection

Using Application-Scoped Connectors

Inbound Communication Support

Outbound Communication Support

Configuring a Message Driven Bean to Use a Resource Adapter

12.  Developing Lifecycle Listeners

13.  Developing OSGi-enabled Java EE Applications

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

18.  Using the JavaMail API


Connector Support in the GlassFish Server

The GlassFish Server supports the development and deployment of resource adapters that are compatible with the Connector 1.6 specification (and, for backward compatibility, the Connector 1.0 and 1.5 specifications).

The Connector 1.0 specification defines the outbound connectivity system contracts between the resource adapter and the GlassFish Server. The Connector 1.5 specification introduces major additions in defining system level contracts between the GlassFish Server and the resource adapter with respect to inbound connectivity, life cycle management, and thread management. The Connector 1.6 specification introduces further additions in defining system level contracts between the GlassFish Server and the resource adapter with respect to the following:

Connector Architecture for JMS and JDBC

In the Administration Console, connector, JMS, and JDBC resources are handled differently, but they use the same underlying Connector architecture. In the GlassFish Server, all communication to an EIS, whether to a message provider or an RDBMS, happens through the Connector architecture. To provide JMS infrastructure to clients, the GlassFish Server uses the GlassFish Server Message Queue software. To provide JDBC infrastructure to clients, the GlassFish Server uses its own JDBC system resource adapters. The GlassFish Server automatically makes these system resource adapters available to any client that requires them.

For more information about JMS in the GlassFish Server, see Chapter 17, Using the Java Message Service. For more information about JDBC in the GlassFish Server, see Chapter 14, Using the JDBC API for Database Access.

Connector Configuration

The GlassFish Server does not need to use sun-ra.xml, which previous GlassFish Server versions used, to store server-specific deployment information inside a Resource Adapter Archive (RAR) file. (However, the sun-ra.xml file is still supported for backward compatibility.) Instead, the information is stored in the server configuration. As a result, you can create multiple connector connection pools for a connection definition in a functional resource adapter instance, and you can create multiple user-accessible connector resources (that is, registering a resource with a JNDI name) for a connector connection pool. In addition, dynamic changes can be made to connector connection pools and the connector resource properties without restarting the GlassFish Server.