Note, in terms of 'generated' values, the Ant copy task coupled with a filter
set is a decent solution. Again, have a look at the JCA example code for a
starting point.
On Aug 29, 2012, at 2:04 PM, Weston M. Price wrote:
>
> On Aug 29, 2012, at 1:58 PM, Dan Carda wrote:
>
>>
>> I have a (hopefully easy) question about MDB annotation.
>>
>> For the parameter connectionURL we have a different broker for DEV, UAT, and
>> Prod. What's the syntax to change that static text to a variable.
>>
>> (Sorry, I know that's easy but this part is a bit new to me.)
> Good question. Unfortunately this is not easy to change without actually
> modifying code. One thing you could do, and we do this in our example code,
> is either use some form of generated build system or remove the annotation
> and modify the jboss descriptors to include the connectionURL param and
> value. I am thinking of ways to make this easier to manage but unfortunately,
> right now it's a bit more manual than I would like.
>
> Regards,
>
> Weston
>
>
>>
>> @MessageDriven ( activationConfig = {
>>
>> @ActivationConfigProperty (
>> propertyName = "acknowledgeMode",
>> propertyValue = "Auto-acknowledge"
>> ) , @ActivationConfigProperty (
>> propertyName = "destinationType",
>> propertyValue = "javax.jms.Queue"
>> ) , @ActivationConfigProperty (
>> propertyName = "destination",
>> propertyValue = "java:jboss/exported/SasRequestQueue"
>> ) , @ActivationConfigProperty (
>> propertyName = "connectionURL",
>> propertyValue =
>> "amqp://guest:guest@clientid/test?brokerlist='tcp://devbusn4:1234''"
>> ) , @ActivationConfigProperty (
>> propertyName = "subscriptionDurability",
>> propertyValue = "NotDurable"
>> ) , @ActivationConfigProperty (
>> propertyName = "maxSession",
>> propertyValue = "1"
>> )
>> } )
>>
>> Many Thanks,
>> Daniel Carda
>> TW Telecom
>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Question-About-Annotation-tp34348254p34348254.html
>> Sent from the Qpid Developers mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
