camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: extending Camel by implementing your own custom EIP?
Date Thu, 19 May 2011 08:01:35 GMT
Just implement your own Processor, and use .process in the DSL.

If you want to introduce new keywords in the DSL, you need to either
- extend RouteBuilder and offer that in Java DSL only. And requre end
user to use your custom RouteBuilder
- change the source code in camel-core to introduce the EIP in the
model package.
- use some dynamic language like scala / groovy to extend and
introduce new EIP keywords.

On Thu, May 19, 2011 at 9:55 AM, janne postilista
<> wrote:
> Can I extend Camel by implementing my own custom EIP
> I have a case where all messages A need to be delayed if message
> B-start has arrived, until message B-end arrives, when all messages A
> should be sent forward. This may or may not be doable using
> resequencer, I am not sure about it since the rules related delaying
> are a bit more complicated than that. In any case, the current
> resequencer wont work, since it's state would need to be persistent
> How difficult would rolling out your own such EIP be?

Claus Ibsen
CamelOne 2011:
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message