camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Abstracting Routes using Components
Date Wed, 27 Oct 2010 08:45:09 GMT
Hi Kristof

Just wanted to say great work and a nice debate you have started.

I have only had the time to skim read, but so many great minds is
already debating this.
So keep in there and I am sure we will get some great new feature in
Camel based on your work.

On Sun, Oct 24, 2010 at 11:19 PM, kristofsajdak
<> wrote:
> Hi,
> I'm currently working on a poc for a customer.
> As part of their core business they offer a platform which mediates between
> trading partners.
> What is special about their use case is the fact that they want the actual
> routes between
> partners to be defined by employees with limited technical knowledge
> (solution consultants).
> I know there is the xml dsl and the upcoming camel rider which lowers the
> threshold for non developers.
> But even when using these features, the route configuration would be way too
> fine grained for them and
> they would still require too much knowledge on the details of the technical
> components.
> Last week I was at the FUSE community day in Paris and spoke to James
> Strachan on the customer
> need to abstract some parts of the routes. He mentioned the idea of using a
> component as a kind
> of proxy for a route.
> I believe this is a real nice solution to the problem.
> A complex route were a pdf is generated from an xml using xslt and fop and
> the result is signed using a
> third party service exposed over http could be reduced to the following.
>        <route>
>            <from uri="{{}}"/>
>            <to
> uri="route:generateAndSignPdf?signatureReason=JustForFun&amp;signatureVisible=true&amp;xslUri=com/xti/poc/camel/route/sample1/krusty.xsl"/>
>            <to uri="{{data.out}}"/>
>        </route>
> The route component concept abstracts the route low level technical details
> and makes reuse easy.
> The solution consultant only needs to define the route:generateAndSignPdf
> with the correct parameters.
> As this construct would provide great value to the customer I went ahead and
> implemented this idea as part of the poc. Attached to this post is my
> codebase with a unit test executing the scenario mentioned above.
> I would really appreciate some feedback from the community on the code I
> wrote.
> I tried fitting this in with the component lifecycle the best I could but
> still have some doubts on whether it's done correct.
> Getting an expert opinion on this would be a big help.
> Best regards,
> Kristof
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Twitter: davsclaus
Author of Camel in Action:

View raw message