Hi Freeman,
Yes, I know I can use other JMS implementations. However, my JMS
implementation does not create a dynamic queue on jndiDestinationName lookup
like ActiveMQ does. Rather, it does not allow dynamic queues to be looked-up
via jndi. Instead, one uses a jmsProviderDestinationName instead of a
jndiDestinationName to cause a dynamic queue to be created. Can I configure
CXF with a jmsProviderDestinationName instead of a jndiDestinationName?
- Ron
Freeman Fang wrote:
>
> Hi Ron,
> Same as Cxf, servicemix-cxf-bc/jms transport can use different jms
> implementation besides ActiveMQ underlying.
> You can specify your jndi provider by means of
> <jms:address ...>
> ...
> <jms:JMSNamingProperty name="java.naming.factory.initial" value="jndi
> provider class"/> ("it's
> org.apache.activemq.jndi.ActiveMQInitialContextFactory for AMQ, but
> other jms implementations should have their own")
> </jms:address>
>
> [1] for more about the jms transport configuration
> [1]http://cwiki.apache.org/CXF20DOC/jms-transport.html
>
> Regards
>
> Freeman
>
> Ron Gavlin wrote:
>> I have a CXF-BC Consumer w/JMS transport that I want to listen on a
>> non-ActiveMQ dynamic queue. smx-jms provides a property named
>> "jmsProviderDestinationName" which, if used, causes the target JMS
>> destination to be created by the JMS provider by calling
>> Session.createQueue. The CXF-BC Consumer w/JMS transport does not seem to
>> provide a comparable "jmsProviderDestinationName" property. Rather, it
>> seems to only support a jndiDestinationName which, if used with a
>> non-ActiveMQ dynamic queue, causes a JNDI lookup error. Is this a CXF
>> issue or a SMX-CXF-BC issue? Any suggestions on how to work-around this
>> problem?
>>
>> Thanks,
>>
>> - Ron
>>
>>
>
>
>
--
View this message in context:
http://www.nabble.com/smx-cxf-bc-consumer-w-jms-transport-and-non-jndiDestinationName-tp18475778p18479112.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
