You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Marek2009 <Ma...@icw.de> on 2009/06/26 23:39:09 UTC
"Trash bin" endpoint?
Hello,
I would like to achieve this in a route: Discarding a message based on a
specific criteria.
I know: This is what Message Filter pattern and the .filter() clause do, but
I would rather use .choice()-.when() followed by something like
".to('trashbin:trashbin-endpoint')". This approach ("filtering by content
routing") appears to have the following advantage: If I later decide to
actually _use_ these messages instead of discarding them, I do not have to
modify any predicates or re-arrange filter clauses, I just have to touch one
single ".to()" clause.
My question: Is there a "trash bin" component/endpoint in Camel?
I tried to use a "dead end" direct endpoint for this purpose, i. e. a direct
endpoint associated with no ".from()" clause whatsover. But I am not sure,
if this has any side effects. The message just should get discarded without
any redelivery attempts, errors or warnings, the exchange should be
considered completed. This should also work for InOut exchanges.
1) Does it make sense?
2) Is there a means to do it in Camel? If so: Which version?
3) If there are multiple ways to do it, what would be the most "elegant"
one, the "best practice"?
Any feedback will be greatly appreciated. :-)
Kind Regards
Marek
--
View this message in context: http://www.nabble.com/%22Trash-bin%22-endpoint--tp24227620p24227620.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: "Trash bin" endpoint?
Posted by Marek2009 <Ma...@icw.de>.
Hi folks,
many thanks for the tips. To implement a "trashbin sink" in my Camel 1.6
route I tried out a few constructs, among others a null file, a direct
endpoint and a SEDA endpoint.
At last, the following (Groovy) code yielded a behaviour I was satisfied
with - no observed side effects, no exceptions, no warnings.
.choice()
.when{ ...}
...
.when{ ...}
.to('direct:custom-channel-purger')
builder
.from('direct:custom-channel-purger')
.process{it.in.body = ''}
.filter{false}
In my particular route endpoints expecting a response (HTTP, MLLP) protested
when a message was discarded. The HTTP server endpoint (Jetty) complained:
"org.apache.camel.NoTypeConversionAvailableException: No type converter
available to convert from type: class org.apache.camel.impl.DefaultMessage
to the required type: java.io.InputStream..." I was also getting warnings
from my HL7 MLLP (mina) endpoint:
"org.apache.mina.filter.codec.ProtocolEncoderException".
Thus I added an empty string body to be used as a response.
--
View this message in context: http://www.nabble.com/%22Trash-bin%22-endpoint--tp24227620p24708404.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: "Trash bin" endpoint?
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
We could use the seda endpoint as trashbin. We could add an option to
allow it to ignore messages that exceed the queue limit. Then the end
user can provide a queue size of 1 or 0 to not keep the exchanges in
memory.
On Sat, Jun 27, 2009 at 6:45 PM, Claus Ibsen<cl...@gmail.com> wrote:
> On Sat, Jun 27, 2009 at 3:47 PM, Hadrian Zbarcea<hz...@gmail.com> wrote:
>> I am not sure a new dev null feature is needed. I think it's already there
>> for you to use.
>>
>>>>> If I later decide to
>>>>> actually _use_ these messages instead of discarding them, I do not have
>>>>> to
>>>>> modify any predicates or re-arrange filter clauses, I just have to touch
>>>>> one
>>>>> single ".to()" clause.
>>
>>
>> If messages are sent to dev null they won't be available for further
>> processing. And discarding is an implicit feature of camel, if you don't do
>> anything with them they get discarded. Try something like:
>>
>> from(endpoint).filter(body().isNull());
> yeah that is right but you then need a Filter DSL to do this.
> What he wanted was an endpoint. In which he dynamic can change at
> runtime / configuration time.
> For instance using spring property placeholders etc.
>
> So with an endpoint you could filter / trash out messages. And keep
> the route DSL as is.
> And then eg configure the endpoint differently eg in production and
> use a real "non trash" endpoint.
>
>
>
>
>>
>> And send any message with a non null body. The messages will just
>> disappear. What you ask makes sense for InOut messages as well, but you're
>> still responsible for producing the output message to send to the client.
>>
>> Cheers,
>> Hadrian
>>
>> On Jun 27, 2009, at 2:41 AM, Claus Ibsen wrote:
>>
>>> Hi
>>>
>>> Its not to bad with a "null" component to send it to dev null. Named
>>> trashbin or devnull or whatever is a good name.
>>>
>>> You can do this in camel 2.0
>>>
>>> to("direct:trash")
>>>
>>> from("direct:trash").stop();
>>>
>>> It requires however that 2nd route to read from it otherwise you get
>>> WARN logs about no consumer to read from it.
>>>
>>>
>>> On Sat, Jun 27, 2009 at 5:27 AM, Hadrian Zbarcea<hz...@gmail.com>
>>> wrote:
>>>>
>>>> The short answer:
>>>>
>>>>> 1) Does it make sense?
>>>>
>>>> Yes, kinda.
>>>>
>>>>> 2) Is there a means to do it in Camel? If so: Which version?
>>>>
>>>> Yes, absolutely.
>>>>
>>>>> 3) If there are multiple ways to do it, what would be the most "elegant"
>>>>> one, the "best practice"?
>>>>
>>>> Whatever fits you. I don't think there is a best practice for such case.
>>>> An easy way to achieve this is:
>>>>
>>>> from(start).choice().when(condition).process(anythingyouwant).otherwise().to("file:trash-bin");
>>>> Where trash-bin is a directory on your file system.
>>>>
>>>> This feature exists in camel from the beginning.
>>>>
>>>> In the case of a choice() for instance there is the otherwise() path for
>>>> messages that do not meet any of your criteria defined by when(). As far
>>>> as
>>>> persistence of such messages goes, it is up to you to decide where to
>>>> keep
>>>> them until you decide what to do with them, and for that you have seda:
>>>> queues or you could use more robust jms: queues or you could use a file:
>>>> or
>>>> ftp: filesystem or even smtp: mail servers. You can retrieve your
>>>> messages
>>>> from there later. So there is no trash bin per se, but you can create
>>>> your
>>>> own, whenever and however you like.
>>>>
>>>> I hope this helps.
>>>> Hadrian
>>>>
>>>>
>>>> On Jun 26, 2009, at 5:39 PM, Marek2009 wrote:
>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>> I would like to achieve this in a route: Discarding a message based on a
>>>>> specific criteria.
>>>>>
>>>>> I know: This is what Message Filter pattern and the .filter() clause do,
>>>>> but
>>>>> I would rather use .choice()-.when() followed by something like
>>>>> ".to('trashbin:trashbin-endpoint')". This approach ("filtering by
>>>>> content
>>>>> routing") appears to have the following advantage: If I later decide to
>>>>> actually _use_ these messages instead of discarding them, I do not have
>>>>> to
>>>>> modify any predicates or re-arrange filter clauses, I just have to touch
>>>>> one
>>>>> single ".to()" clause.
>>>>>
>>>>> My question: Is there a "trash bin" component/endpoint in Camel?
>>>>>
>>>>> I tried to use a "dead end" direct endpoint for this purpose, i. e. a
>>>>> direct
>>>>> endpoint associated with no ".from()" clause whatsover. But I am not
>>>>> sure,
>>>>> if this has any side effects. The message just should get discarded
>>>>> without
>>>>> any redelivery attempts, errors or warnings, the exchange should be
>>>>> considered completed. This should also work for InOut exchanges.
>>>>>
>>>>> 1) Does it make sense?
>>>>> 2) Is there a means to do it in Camel? If so: Which version?
>>>>> 3) If there are multiple ways to do it, what would be the most "elegant"
>>>>> one, the "best practice"?
>>>>>
>>>>> Any feedback will be greatly appreciated. :-)
>>>>>
>>>>> Kind Regards
>>>>>
>>>>> Marek
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/%22Trash-bin%22-endpoint--tp24227620p24227620.html
>>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> Apache Camel Committer
>>>
>>> Open Source Integration: http://fusesource.com
>>> Blog: http://davsclaus.blogspot.com/
>>> Twitter: http://twitter.com/davsclaus
>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: "Trash bin" endpoint?
Posted by Claus Ibsen <cl...@gmail.com>.
On Sat, Jun 27, 2009 at 3:47 PM, Hadrian Zbarcea<hz...@gmail.com> wrote:
> I am not sure a new dev null feature is needed. I think it's already there
> for you to use.
>
>>>> If I later decide to
>>>> actually _use_ these messages instead of discarding them, I do not have
>>>> to
>>>> modify any predicates or re-arrange filter clauses, I just have to touch
>>>> one
>>>> single ".to()" clause.
>
>
> If messages are sent to dev null they won't be available for further
> processing. And discarding is an implicit feature of camel, if you don't do
> anything with them they get discarded. Try something like:
>
> from(endpoint).filter(body().isNull());
yeah that is right but you then need a Filter DSL to do this.
What he wanted was an endpoint. In which he dynamic can change at
runtime / configuration time.
For instance using spring property placeholders etc.
So with an endpoint you could filter / trash out messages. And keep
the route DSL as is.
And then eg configure the endpoint differently eg in production and
use a real "non trash" endpoint.
>
> And send any message with a non null body. The messages will just
> disappear. What you ask makes sense for InOut messages as well, but you're
> still responsible for producing the output message to send to the client.
>
> Cheers,
> Hadrian
>
> On Jun 27, 2009, at 2:41 AM, Claus Ibsen wrote:
>
>> Hi
>>
>> Its not to bad with a "null" component to send it to dev null. Named
>> trashbin or devnull or whatever is a good name.
>>
>> You can do this in camel 2.0
>>
>> to("direct:trash")
>>
>> from("direct:trash").stop();
>>
>> It requires however that 2nd route to read from it otherwise you get
>> WARN logs about no consumer to read from it.
>>
>>
>> On Sat, Jun 27, 2009 at 5:27 AM, Hadrian Zbarcea<hz...@gmail.com>
>> wrote:
>>>
>>> The short answer:
>>>
>>>> 1) Does it make sense?
>>>
>>> Yes, kinda.
>>>
>>>> 2) Is there a means to do it in Camel? If so: Which version?
>>>
>>> Yes, absolutely.
>>>
>>>> 3) If there are multiple ways to do it, what would be the most "elegant"
>>>> one, the "best practice"?
>>>
>>> Whatever fits you. I don't think there is a best practice for such case.
>>> An easy way to achieve this is:
>>>
>>> from(start).choice().when(condition).process(anythingyouwant).otherwise().to("file:trash-bin");
>>> Where trash-bin is a directory on your file system.
>>>
>>> This feature exists in camel from the beginning.
>>>
>>> In the case of a choice() for instance there is the otherwise() path for
>>> messages that do not meet any of your criteria defined by when(). As far
>>> as
>>> persistence of such messages goes, it is up to you to decide where to
>>> keep
>>> them until you decide what to do with them, and for that you have seda:
>>> queues or you could use more robust jms: queues or you could use a file:
>>> or
>>> ftp: filesystem or even smtp: mail servers. You can retrieve your
>>> messages
>>> from there later. So there is no trash bin per se, but you can create
>>> your
>>> own, whenever and however you like.
>>>
>>> I hope this helps.
>>> Hadrian
>>>
>>>
>>> On Jun 26, 2009, at 5:39 PM, Marek2009 wrote:
>>>
>>>>
>>>> Hello,
>>>>
>>>> I would like to achieve this in a route: Discarding a message based on a
>>>> specific criteria.
>>>>
>>>> I know: This is what Message Filter pattern and the .filter() clause do,
>>>> but
>>>> I would rather use .choice()-.when() followed by something like
>>>> ".to('trashbin:trashbin-endpoint')". This approach ("filtering by
>>>> content
>>>> routing") appears to have the following advantage: If I later decide to
>>>> actually _use_ these messages instead of discarding them, I do not have
>>>> to
>>>> modify any predicates or re-arrange filter clauses, I just have to touch
>>>> one
>>>> single ".to()" clause.
>>>>
>>>> My question: Is there a "trash bin" component/endpoint in Camel?
>>>>
>>>> I tried to use a "dead end" direct endpoint for this purpose, i. e. a
>>>> direct
>>>> endpoint associated with no ".from()" clause whatsover. But I am not
>>>> sure,
>>>> if this has any side effects. The message just should get discarded
>>>> without
>>>> any redelivery attempts, errors or warnings, the exchange should be
>>>> considered completed. This should also work for InOut exchanges.
>>>>
>>>> 1) Does it make sense?
>>>> 2) Is there a means to do it in Camel? If so: Which version?
>>>> 3) If there are multiple ways to do it, what would be the most "elegant"
>>>> one, the "best practice"?
>>>>
>>>> Any feedback will be greatly appreciated. :-)
>>>>
>>>> Kind Regards
>>>>
>>>> Marek
>>>>
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/%22Trash-bin%22-endpoint--tp24227620p24227620.html
>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: "Trash bin" endpoint?
Posted by Hadrian Zbarcea <hz...@gmail.com>.
I am not sure a new dev null feature is needed. I think it's already
there for you to use.
>>> If I later decide to
>>> actually _use_ these messages instead of discarding them, I do not
>>> have to
>>> modify any predicates or re-arrange filter clauses, I just have to
>>> touch
>>> one
>>> single ".to()" clause.
If messages are sent to dev null they won't be available for further
processing. And discarding is an implicit feature of camel, if you
don't do anything with them they get discarded. Try something like:
from(endpoint).filter(body().isNull());
And send any message with a non null body. The messages will just
disappear. What you ask makes sense for InOut messages as well, but
you're still responsible for producing the output message to send to
the client.
Cheers,
Hadrian
On Jun 27, 2009, at 2:41 AM, Claus Ibsen wrote:
> Hi
>
> Its not to bad with a "null" component to send it to dev null. Named
> trashbin or devnull or whatever is a good name.
>
> You can do this in camel 2.0
>
> to("direct:trash")
>
> from("direct:trash").stop();
>
> It requires however that 2nd route to read from it otherwise you get
> WARN logs about no consumer to read from it.
>
>
> On Sat, Jun 27, 2009 at 5:27 AM, Hadrian Zbarcea<hz...@gmail.com>
> wrote:
>> The short answer:
>>
>>> 1) Does it make sense?
>>
>> Yes, kinda.
>>
>>> 2) Is there a means to do it in Camel? If so: Which version?
>>
>> Yes, absolutely.
>>
>>> 3) If there are multiple ways to do it, what would be the most
>>> "elegant"
>>> one, the "best practice"?
>>
>> Whatever fits you. I don't think there is a best practice for such
>> case.
>> An easy way to achieve this is:
>> from
>> (start
>> ).choice
>> ().when
>> (condition).process(anythingyouwant).otherwise().to("file:trash-
>> bin");
>> Where trash-bin is a directory on your file system.
>>
>> This feature exists in camel from the beginning.
>>
>> In the case of a choice() for instance there is the otherwise()
>> path for
>> messages that do not meet any of your criteria defined by when().
>> As far as
>> persistence of such messages goes, it is up to you to decide where
>> to keep
>> them until you decide what to do with them, and for that you have
>> seda:
>> queues or you could use more robust jms: queues or you could use a
>> file: or
>> ftp: filesystem or even smtp: mail servers. You can retrieve your
>> messages
>> from there later. So there is no trash bin per se, but you can
>> create your
>> own, whenever and however you like.
>>
>> I hope this helps.
>> Hadrian
>>
>>
>> On Jun 26, 2009, at 5:39 PM, Marek2009 wrote:
>>
>>>
>>> Hello,
>>>
>>> I would like to achieve this in a route: Discarding a message
>>> based on a
>>> specific criteria.
>>>
>>> I know: This is what Message Filter pattern and the .filter()
>>> clause do,
>>> but
>>> I would rather use .choice()-.when() followed by something like
>>> ".to('trashbin:trashbin-endpoint')". This approach ("filtering by
>>> content
>>> routing") appears to have the following advantage: If I later
>>> decide to
>>> actually _use_ these messages instead of discarding them, I do not
>>> have to
>>> modify any predicates or re-arrange filter clauses, I just have to
>>> touch
>>> one
>>> single ".to()" clause.
>>>
>>> My question: Is there a "trash bin" component/endpoint in Camel?
>>>
>>> I tried to use a "dead end" direct endpoint for this purpose, i.
>>> e. a
>>> direct
>>> endpoint associated with no ".from()" clause whatsover. But I am
>>> not sure,
>>> if this has any side effects. The message just should get discarded
>>> without
>>> any redelivery attempts, errors or warnings, the exchange should be
>>> considered completed. This should also work for InOut exchanges.
>>>
>>> 1) Does it make sense?
>>> 2) Is there a means to do it in Camel? If so: Which version?
>>> 3) If there are multiple ways to do it, what would be the most
>>> "elegant"
>>> one, the "best practice"?
>>>
>>> Any feedback will be greatly appreciated. :-)
>>>
>>> Kind Regards
>>>
>>> Marek
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/%22Trash-bin%22-endpoint--tp24227620p24227620.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
Re: "Trash bin" endpoint?
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Its not to bad with a "null" component to send it to dev null. Named
trashbin or devnull or whatever is a good name.
You can do this in camel 2.0
to("direct:trash")
from("direct:trash").stop();
It requires however that 2nd route to read from it otherwise you get
WARN logs about no consumer to read from it.
On Sat, Jun 27, 2009 at 5:27 AM, Hadrian Zbarcea<hz...@gmail.com> wrote:
> The short answer:
>
>> 1) Does it make sense?
>
> Yes, kinda.
>
>> 2) Is there a means to do it in Camel? If so: Which version?
>
> Yes, absolutely.
>
>> 3) If there are multiple ways to do it, what would be the most "elegant"
>> one, the "best practice"?
>
> Whatever fits you. I don't think there is a best practice for such case.
> An easy way to achieve this is:
> from(start).choice().when(condition).process(anythingyouwant).otherwise().to("file:trash-bin");
> Where trash-bin is a directory on your file system.
>
> This feature exists in camel from the beginning.
>
> In the case of a choice() for instance there is the otherwise() path for
> messages that do not meet any of your criteria defined by when(). As far as
> persistence of such messages goes, it is up to you to decide where to keep
> them until you decide what to do with them, and for that you have seda:
> queues or you could use more robust jms: queues or you could use a file: or
> ftp: filesystem or even smtp: mail servers. You can retrieve your messages
> from there later. So there is no trash bin per se, but you can create your
> own, whenever and however you like.
>
> I hope this helps.
> Hadrian
>
>
> On Jun 26, 2009, at 5:39 PM, Marek2009 wrote:
>
>>
>> Hello,
>>
>> I would like to achieve this in a route: Discarding a message based on a
>> specific criteria.
>>
>> I know: This is what Message Filter pattern and the .filter() clause do,
>> but
>> I would rather use .choice()-.when() followed by something like
>> ".to('trashbin:trashbin-endpoint')". This approach ("filtering by content
>> routing") appears to have the following advantage: If I later decide to
>> actually _use_ these messages instead of discarding them, I do not have to
>> modify any predicates or re-arrange filter clauses, I just have to touch
>> one
>> single ".to()" clause.
>>
>> My question: Is there a "trash bin" component/endpoint in Camel?
>>
>> I tried to use a "dead end" direct endpoint for this purpose, i. e. a
>> direct
>> endpoint associated with no ".from()" clause whatsover. But I am not sure,
>> if this has any side effects. The message just should get discarded
>> without
>> any redelivery attempts, errors or warnings, the exchange should be
>> considered completed. This should also work for InOut exchanges.
>>
>> 1) Does it make sense?
>> 2) Is there a means to do it in Camel? If so: Which version?
>> 3) If there are multiple ways to do it, what would be the most "elegant"
>> one, the "best practice"?
>>
>> Any feedback will be greatly appreciated. :-)
>>
>> Kind Regards
>>
>> Marek
>>
>> --
>> View this message in context:
>> http://www.nabble.com/%22Trash-bin%22-endpoint--tp24227620p24227620.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: "Trash bin" endpoint?
Posted by Hadrian Zbarcea <hz...@gmail.com>.
The short answer:
> 1) Does it make sense?
Yes, kinda.
> 2) Is there a means to do it in Camel? If so: Which version?
Yes, absolutely.
> 3) If there are multiple ways to do it, what would be the most
> "elegant"
> one, the "best practice"?
Whatever fits you. I don't think there is a best practice for such
case. An easy way to achieve this is:
from
(start
).choice
().when(condition).process(anythingyouwant).otherwise().to("file:trash-
bin");
Where trash-bin is a directory on your file system.
This feature exists in camel from the beginning.
In the case of a choice() for instance there is the otherwise() path
for messages that do not meet any of your criteria defined by when().
As far as persistence of such messages goes, it is up to you to decide
where to keep them until you decide what to do with them, and for that
you have seda: queues or you could use more robust jms: queues or you
could use a file: or ftp: filesystem or even smtp: mail servers. You
can retrieve your messages from there later. So there is no trash bin
per se, but you can create your own, whenever and however you like.
I hope this helps.
Hadrian
On Jun 26, 2009, at 5:39 PM, Marek2009 wrote:
>
> Hello,
>
> I would like to achieve this in a route: Discarding a message based
> on a
> specific criteria.
>
> I know: This is what Message Filter pattern and the .filter() clause
> do, but
> I would rather use .choice()-.when() followed by something like
> ".to('trashbin:trashbin-endpoint')". This approach ("filtering by
> content
> routing") appears to have the following advantage: If I later decide
> to
> actually _use_ these messages instead of discarding them, I do not
> have to
> modify any predicates or re-arrange filter clauses, I just have to
> touch one
> single ".to()" clause.
>
> My question: Is there a "trash bin" component/endpoint in Camel?
>
> I tried to use a "dead end" direct endpoint for this purpose, i. e.
> a direct
> endpoint associated with no ".from()" clause whatsover. But I am not
> sure,
> if this has any side effects. The message just should get discarded
> without
> any redelivery attempts, errors or warnings, the exchange should be
> considered completed. This should also work for InOut exchanges.
>
> 1) Does it make sense?
> 2) Is there a means to do it in Camel? If so: Which version?
> 3) If there are multiple ways to do it, what would be the most
> "elegant"
> one, the "best practice"?
>
> Any feedback will be greatly appreciated. :-)
>
> Kind Regards
>
> Marek
>
> --
> View this message in context: http://www.nabble.com/%22Trash-bin%22-endpoint--tp24227620p24227620.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>