Part I Development Tasks and Tools
1. Setting Up a Development Environment
Part II Developing Applications and Application Components
6. Using the Java Persistence API
7. Developing Web Applications
8. Using Enterprise JavaBeans Technology
9. Using Container-Managed Persistence
Connector Support in the GlassFish Server
Connector Architecture for JMS and JDBC
Advanced Connector Configuration Options
Overriding Configuration Properties
Testing a Connector Connection Pool
Flushing a Connector Connection Pool
Specifying the Class Loading Policy
Using Last Agent Optimization of Transactions
Disabling Pooling for a Connection
Using Application-Scoped Connectors
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
The Connector specification defines the system contracts for achieving outbound connectivity from an EIS. A resource adapter supporting outbound communication provides an instance of a ManagedConnectionFactory JavaBean class. A ManagedConnectionFactory JavaBean represents outbound connectivity information to an EIS instance from an application.
The 1.6 Connector specification introduces a mechanism through which the transaction level of a ManagedConnectionFactory can be detected at runtime. During the configuration of a ManagedConnectionFactory in the Connector Connection Pools page in the Administration Console, the Administration Console can instantiate the ManagedConnectionFactory and show the level of transaction support. The three levels are no-tx, local-tx, xa-tx. If a ManagedConnectionFactory returns local-tx as the level it can support, it is assumed that xa-tx is not supported, and the Administration Console shows only no-tx and local-tx as the available support levels.
For more information, click the Help button in the Administration Console.