public class DefaultJmsActivationSpecFactory extends StandardJmsActivationSpecFactory
JmsActivationSpecFactory
interface.
Supports the standard JMS properties as defined by the JCA 1.5 specification,
as well as Spring's extended "maxConcurrency" and "prefetchSize" settings
through autodetection of well-known vendor-specific provider properties.
An ActivationSpec factory is effectively dependent on the concrete JMS provider, e.g. on ActiveMQ. This default implementation simply guesses the ActivationSpec class name from the provider's class name ("ActiveMQResourceAdapter" -> "ActiveMQActivationSpec" in the same package, or "ActivationSpecImpl" in the same package as the ResourceAdapter class), and populates the ActivationSpec properties as suggested by the JCA 1.5 specification (Appendix B). Specify the 'activationSpecClass' property explicitly if these default naming rules do not apply.
Note: ActiveMQ, JORAM and WebSphere are supported in terms of extended settings (through the detection of their bean property naming conventions). The default ActivationSpec class detection rules may apply to other JMS providers as well.
Thanks to Agim Emruli and Laurie Chan for pointing out WebSphere MQ settings and contributing corresponding tests!
StandardJmsActivationSpecFactory.setActivationSpecClass(java.lang.Class<?>)
Modifier and Type | Field and Description |
---|---|
protected Log |
logger
Logger available to subclasses
|
Constructor and Description |
---|
DefaultJmsActivationSpecFactory() |
Modifier and Type | Method and Description |
---|---|
protected void |
applyAcknowledgeMode(BeanWrapper bw,
int ackMode)
This implementation maps
SESSION_TRANSACTED onto an
ActivationSpec property named "useRAManagedTransaction", if available
(following ActiveMQ's naming conventions). |
protected Class<?> |
determineActivationSpecClass(ResourceAdapter adapter)
This implementation guesses the ActivationSpec class name from the
provider's class name: e.g.
|
protected void |
populateActivationSpecProperties(BeanWrapper bw,
JmsActivationSpecConfig config)
This implementation supports Spring's extended "maxConcurrency"
and "prefetchSize" settings through detecting corresponding
ActivationSpec properties: "maxSessions"/"maxNumberOfWorks" and
"maxMessagesPerSessions"/"maxMessages", respectively
(following ActiveMQ's and JORAM's naming conventions).
|
createActivationSpec, getDestinationResolver, setActivationSpecClass, setDefaultProperties, setDestinationResolver
protected final Log logger
protected Class<?> determineActivationSpecClass(ResourceAdapter adapter)
determineActivationSpecClass
in class StandardJmsActivationSpecFactory
adapter
- the ResourceAdapter to checknull
if not determinableStandardJmsActivationSpecFactory.setActivationSpecClass(java.lang.Class<?>)
protected void populateActivationSpecProperties(BeanWrapper bw, JmsActivationSpecConfig config)
populateActivationSpecProperties
in class StandardJmsActivationSpecFactory
bw
- the BeanWrapper wrapping the ActivationSpec objectconfig
- the configured object holding common JMS settingsprotected void applyAcknowledgeMode(BeanWrapper bw, int ackMode)
SESSION_TRANSACTED
onto an
ActivationSpec property named "useRAManagedTransaction", if available
(following ActiveMQ's naming conventions).applyAcknowledgeMode
in class StandardJmsActivationSpecFactory
bw
- the BeanWrapper wrapping the ActivationSpec objectackMode
- the configured acknowledge mode
(according to the constants in Session
Session.AUTO_ACKNOWLEDGE
,
Session.DUPS_OK_ACKNOWLEDGE
,
Session.CLIENT_ACKNOWLEDGE
,
Session.SESSION_TRANSACTED