| Exit Print View | |
Sun GlassFish Enterprise Server v3 Application Development Guide |
|
|
|
Part I Development Tasks and Tools
1. Setting Up a Development Environment
3. Using Ant with Enterprise Server
Part II Developing Applications and Application Components
7. Using the Java Persistence API
8. Developing Web Applications
9. Using Enterprise JavaBeans Technology
10. Using Container-Managed Persistence
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
Administration of the JMS Service
Checking Whether the JMS Provider Is Running
Creating Physical Destinations
Creating JMS Resources: Destinations and Connection Factories
Restarting the JMS Client After JMS Configuration
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
The Sun GlassFish Message Queue software is integrated into the Enterprise Server using a resource adapter that is compliant with the Connector specification. The module name of this system resource adapter is jmsra. Every JMS resource is converted to a corresponding connector resource of this resource adapter as follows:
Connection Factory – A connector connection pool with a max-pool-size of 250 and a corresponding connector resource
Destination (Topic or Queue) – A connector administered object
You use connector configuration tools to manage JMS resources. For more information, see
Chapter 12, Developing Connectors.
|
|