SeamFramework.orgCommunity Documentation

Chapter 69. Resource Injection

69.1. JMS Resource Injection
69.1.1. Destination Based Injection
69.1.2. Resource Configuration
69.2. Module Extensions

In this chapter we'll look at how to inject some of the common JMS resource types.

The following JMS resources are available for injection:

Destination-based resources:

The Seam JMS module has certain points of extension, where the application developer can customize the behavior to match their needs. This is done by extending any of three base classes:

This can be done using CDI specializations and extending the base class to change the produced object. This allows the application developer to customize the produced behavior. For example, the base implementation assumes a Java EE container, however an extension to the JmsConnectionFactoryProducer could bootstrap a JMS container for you or change the default JNDI location of the ConnectionFactory

Each producer in these classes generates an instance based on The @JmsDefault annotation. This object is used within other places of the API, so you can control the Session generated that is injected into a MessageManager this way.