Re: Re:Re: Re:Re: How to filter message in virtual destinations?

[hengyunabc]

Without virtual topic, the camel.xml :

        <route id="route_coreservice_datachange"
errorHandlerRef="transactionErrorHandler1">
                <description>coreservice.datachange Route</description>
                <from
                
uri="jms1:topic:VirtualTopic.Orders?clientId=client1&amp;durableSubscriptionName=bar1"
/>
                          <transacted />
                <to uri="jms1:queue:q.A" />
        </route>

With virtual topic, the camel.xml:

        <route id="route_coreservice_datachange"
errorHandlerRef="transactionErrorHandler1">
                <description>coreservice.datachange Route</description>
                <from
                        uri="jms1:queue:Consumer.A.VirtualTopic.Orders " />
                          <transacted />
                <to uri="jms1:queue:q.A" />
        </route>

I can take far away from "unique subscriber name", "clientId".  
The camel.xml will be small and clear. 
In fact, I think that it is hard to configure a right camel.xml while it
contains "subscriber name", "clientId". 



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/How-to-filter-message-in-virtual-destinations-tp4668296p4668453.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.