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


Chapter 11

Developing Connectors

This chapter describes Oracle GlassFish Server support for the Java EE 1.6 Connector Architecture, also known as JSR 322.

The Java EE Connector Architecture provides a Java solution to the problem of connectivity between multiple application servers and existing enterprise information systems (EISs). By using the Java EE Connector architecture, EIS vendors no longer need to customize their product for each application server. Application server vendors who conform to the Java EE Connector architecture do not need to write custom code to add connectivity to a new EIS.

This chapter uses the terms connector and resource adapter interchangeably. Both terms refer to a resource adapter module that is developed in conformance with the Java EE Connector Architecture Specification.

Note - If you installed the Web Profile, connector modules that use only outbound communication features and work-management that does not involve inbound communication features are supported. Other connector features are supported only in the full GlassFish Server.

For more information about connectors, see Java EE Connector Architecture and “Chapter 37: Java EE Connector Architecture” in the The Java EE 6 Tutorial.

For connector examples, see

For information about deploying a connector to the GlassFish Server, see the Oracle GlassFish Server 3.1 Application Deployment Guide.

The following topics are addressed here: