Allows for defining a common JmsActivationSpecConfig object
that gets converted into a provider-specific JCA 1.5 ActivationSpec
object for activating the endpoint.
NOTE: This JCA-based endpoint manager supports standard JMS
MessageListener endpoints only. It does not support
variant, simply because the JCA endpoint management contract does not allow
for obtaining the current JMS Session.
If no transaction manager is specified, the endpoint invocation
will simply not be wrapped in an XA transaction. Consult your
resource provider's ActivationSpec documentation for the local
transaction options of your particular provider.
This is a shortcut for configuring a dedicated JmsMessageEndpointFactory.
Set the factory for concrete JCA 1.5 ActivationSpec objects,
creating JCA ActivationSpecs based on
This factory is dependent on the concrete JMS provider, e.g. on ActiveMQ.
The default implementation simply guesses the ActivationSpec class name
from the provider's class name (e.g. "ActiveMQResourceAdapter" ->
"ActiveMQActivationSpec" in the same package), and populates the
ActivationSpec properties as suggested by the JCA 1.5 specification
(plus a couple of autodetected vendor-specific properties).
beanName - the name of the bean in the factory.
Note that this name is the actual bean name used in the factory, which may
differ from the originally specified name: in particular for inner bean
names, the actual bean name might have been made unique through appending
"#..." suffixes. Use the BeanFactoryUtils.originalBeanName(String)
method to extract the original bean name (without suffix), if desired.