Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of hwellmann.de@gmail.com
 designates 209.85.214.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAH+vQmNH3ak8d0Ud+qq1rZ=XY+U8bjcEkQ48BFdWiu-tysgK9A@mail.gmail.com>
References: 
 <CAC-wabuL4v1Kmhn4t4SV5k3WeFkfCe6vRyLkVFc1EuqKBe8QdQ@mail.gmail.com>
	<CAH+vQmNH3ak8d0Ud+qq1rZ=XY+U8bjcEkQ48BFdWiu-tysgK9A@mail.gmail.com>
Date: Fri, 8 Feb 2013 17:26:12 +0100
Message-ID: 
 <CAC-wabto3DJBbcV0rGuh2ZCgGp++iBr-ZnL9BkhbtwvztsVmmw@mail.gmail.com>
Subject: Re: JNDI destination names in MDBs
From: Harald Wellmann <hwellmann.de@gmail.com>
To: users@activemq.apache.org
Content-Type: text/plain; charset=UTF-8

Here's a JIRA issue: https://issues.apache.org/jira/browse/AMQ-4305

Are you sure about the transformDestination() method you mentioned?
Searching the ActiveMQ source tree, the only occurrences I can find
are in activemq-client, not in activemq-ra. Isn't
ActiveMQEndpointWorker the class that should be changed, doing a JNDI
lookup instead of calling new ActiveMQQueue(destName)?

Best regards,
Harald

2013/2/8 Gary Tully <gary.tully@gmail.com>:
> that is correct. it sounds like a sensible enhancement. can you open a jira
> to track this.
> there is one hook point that could help but it would require replacing a
> class in the rar.
> org.apache.activemq.ActiveMQMessageTransformation#transformDestination gets
> called so that could be used to resolve the provided name via jndi.
>
> that chappy should be configurable like the message transformer -
> http://activemq.apache.org/message-transformation.html
>
>
>
> On 8 February 2013 09:01, Harald Wellmann <hwellmann.de@gmail.com> wrote:
>
>> I'm using ActiveMQ 5.7.0 with JBoss AS 7.1.3 via the activemq-rar
>> resource adapter.
>>
>> The documentation of the MDB activation config properties [1] is a
>> little unspecific, but it seems that the "destination" property has to
>> be the physical queue or topic name, not a JNDI name.
>>
>> Is there any way to make ActiveMQ recognize a JNDI name in this place?
>> Having hard-coded queue names in my application is really a blocker -
>> the queue names depend on the deployment environment and can change at
>> any time.
>>
>> [1] http://activemq.apache.org/activation-spec-properties.html
>>
>> Best regards,
>> Harald
>>
>
>
>
> --
> http://redhat.com
> http://blog.garytully.com