activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikael Falkvidd (JIRA)" <>
Subject [jira] [Commented] (AMQ-4305) Support destination lookup by JNDI name in resource adapter
Date Sun, 10 Feb 2013 21:13:12 GMT


Mikael Falkvidd commented on AMQ-4305:

Tested with JBoss AS 7.2.0.Alpha1-SNAPSHOT from 2013-02-08 and activemq-rar-5.7.0 with this
patch applied, works like a charm.
This enables us to configure different queues for our prod and dev machines without changing
the code/annotations.
> Support destination lookup by JNDI name in resource adapter
> -----------------------------------------------------------
>                 Key: AMQ-4305
>                 URL:
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: JCA Container
>    Affects Versions: 5.7.0
>            Reporter: Harald Wellmann
>         Attachments: AMQ-4305.patch
> 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:

View raw message