You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by mistrz <gr...@edmunds.com> on 2009/12/18 21:14:42 UTC
Interceptors implementaion
We want to post messages to a Virtual Topic (ActiveMQ) and some queues not to
receive the message based on the headers. The Camel Interceptors actually
allow the message to get to the queue, is that correct? If yes, that is not
optimal--any other solutions?
--
View this message in context: http://old.nabble.com/Interceptors-implementaion-tp26849086p26849086.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Interceptors implementaion
Posted by Claus Ibsen <cl...@gmail.com>.
On Sun, Dec 20, 2009 at 9:45 PM, mistrz <gr...@edmunds.com> wrote:
>
> I understand that selectors and filters accomplish the task. The issue is
> that messages are posted to the queue and THEN filtered out. In certain
> situations that can be a significant performance problem.
>
If you do NOT want Camel to consume the unwanted messages from the
topic, then you need to resolve that on the broker side.
So it wont "expose" those unwanted messages to certain clients. Using
the JMS message selector can do that.
But AMQ or other brokers may have more advanced features for that. You
should go ask in the AMQ user forum about this.
>
> Claus Ibsen-2 wrote:
>>
>> Hi
>>
>> On Fri, Dec 18, 2009 at 9:14 PM, mistrz <gr...@edmunds.com> wrote:
>>>
>>> We want to post messages to a Virtual Topic (ActiveMQ) and some queues
>>> not to
>>> receive the message based on the headers. The Camel Interceptors
>>> actually
>>> allow the message to get to the queue, is that correct? If yes, that is
>>> not
>>> optimal--any other solutions?
>>> --
>>
>> I do not understand what you want? Can you explain a bit more what you
>> want?
>>
>>
>> In JMS you can use SQL like selects to filter out messages you do not want
>>
>> Its standard in JMS
>> http://activemq.apache.org/selectors.html
>> http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html
>>
>> With Camel you can use the Message Filter EIP to filter out unwanted
>> messages
>> http://camel.apache.org/message-filter.html
>>
>>
>>
>>> View this message in context:
>>> http://old.nabble.com/Interceptors-implementaion-tp26849086p26849086.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Author of Camel in Action: http://www.manning.com/ibsen/
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>>
>>
>
> --
> View this message in context: http://old.nabble.com/Interceptors-implementaion-tp26849086p26867148.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: Interceptors implementaion
Posted by mistrz <gr...@edmunds.com>.
I understand that selectors and filters accomplish the task. The issue is
that messages are posted to the queue and THEN filtered out. In certain
situations that can be a significant performance problem.
Claus Ibsen-2 wrote:
>
> Hi
>
> On Fri, Dec 18, 2009 at 9:14 PM, mistrz <gr...@edmunds.com> wrote:
>>
>> We want to post messages to a Virtual Topic (ActiveMQ) and some queues
>> not to
>> receive the message based on the headers. The Camel Interceptors
>> actually
>> allow the message to get to the queue, is that correct? If yes, that is
>> not
>> optimal--any other solutions?
>> --
>
> I do not understand what you want? Can you explain a bit more what you
> want?
>
>
> In JMS you can use SQL like selects to filter out messages you do not want
>
> Its standard in JMS
> http://activemq.apache.org/selectors.html
> http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html
>
> With Camel you can use the Message Filter EIP to filter out unwanted
> messages
> http://camel.apache.org/message-filter.html
>
>
>
>> View this message in context:
>> http://old.nabble.com/Interceptors-implementaion-tp26849086p26849086.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Author of Camel in Action: http://www.manning.com/ibsen/
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
>
--
View this message in context: http://old.nabble.com/Interceptors-implementaion-tp26849086p26867148.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Interceptors implementaion
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
On Fri, Dec 18, 2009 at 9:14 PM, mistrz <gr...@edmunds.com> wrote:
>
> We want to post messages to a Virtual Topic (ActiveMQ) and some queues not to
> receive the message based on the headers. The Camel Interceptors actually
> allow the message to get to the queue, is that correct? If yes, that is not
> optimal--any other solutions?
> --
I do not understand what you want? Can you explain a bit more what you want?
In JMS you can use SQL like selects to filter out messages you do not want
Its standard in JMS
http://activemq.apache.org/selectors.html
http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html
With Camel you can use the Message Filter EIP to filter out unwanted messages
http://camel.apache.org/message-filter.html
> View this message in context: http://old.nabble.com/Interceptors-implementaion-tp26849086p26849086.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus