Harald Wellmann created AMQ-4305:
------------------------------------
Summary: Support destination lookup by JNDI name in resource
adapter
Key: AMQ-4305
URL: https://issues.apache.org/jira/browse/AMQ-4305
Project: ActiveMQ
Issue Type: New Feature
Components: JCA Container
Affects Versions: 5.7.0
Reporter: Harald Wellmann
Use Case:
A standalone ActiveMQ broker is integrated with a Java EE 6 server (e.g. JBoss
AS 7.1, GlassFish 3.1) via activemq-rar-5.7.0.rar.
Admin objects corresponding to queues or topics are created at server level,
assigning a JNDI name in addition to the physical destination name.
MDBs are used to handle incoming messages from ActiveMQ destinations. The
destination is specified by
@ActivationConfigProperty(propertyName = "destination", propertyValue =
"physical-destination-name")
Problem:
The physical destination name is now hard-coded in the application. Thus, it is
not possible to deploy the unchanged application in a different runtime
environment where the given destination has a different physical name.
Possible solution:
Create a new activation config property named "destinationJndiName". If this
property is set, the destination is supposed to be registered in JNDI with the
name given by the property value. When this property is set, both
"destinationType" and "destination" are not required.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
