ve seen are based on the properties of the exchange.
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Optional-Endpoints-tp5711824p5711916.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Is it possible to relate to properties in the camel context as well?
All the examples I've seen are based on the properties of the exchange.
--
View this message in context:
http://camel.465427.n5.nabble.com/Optional-Endpoints-tp5711824p5711916.html
Sent from the Camel - Users mailing
e and
schouldn't have a high performance impact as well.
I'll try out right now ...
Patrick
--
View this message in context:
http://camel.465427.n5.nabble.com/Optional-Endpoints-tp5711824p5711880.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Patrick,
take a look at Message Filter EIP, you can configure the filter clause
based on properties loaded using camel:simple language.
att.
*Henrique Viecili*
On Fri, May 18, 2012 at 7:14 AM, prueegg wrote:
> I have a question concerning optional endpoints.
>
> Background is that
I have a question concerning optional endpoints.
Background is that I want to do something like this:
from(anyActiveMQ-Queue)
.bean(anyProcessingBean)
.to(anotherActiveMQ-Queue)
*.to(additionalFileArchiveFolder)*; // optional
if the message should really go to the *additionalFileArchiveFolder
