camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristof Sajdak (JIRA)" <>
Subject [jira] Commented: (CAMEL-3285) Create a new blackbox component which can encapsulate routes using a specialized ProtocolBuilder endpoint (similar to RouteBuilder)
Date Sun, 02 Jan 2011 14:36:47 GMT


Kristof Sajdak commented on CAMEL-3285:

Hi Ashwin,

Browsed through the codebase just now. 
It looks quite flexible, however I feel it might not be a good fit for the use case which
I described a while back in the camel users thread (

To illustrate my point I would like to use the routebuilder which you have defined as part
of your unit tests in the camel-routebox sources.

// Routes
     .to("log:Received request for seda:addToCatalog")
     .to("log:Received request for seda:findBook")
     .to("log:Received request for seda:findAuthor")

using the routebox component to address these routes it could look like the following :
      <from uri="direct://start"/>

        <setHeader headerName="ROUTE_DISPATCH_KEY">
        <to uri="routebox:multipleRoutes?routeBuilders=#bookRoutes&amp;dispatchStrategy=#strategy"/>

This is a little bit complex when you would have to explain this to non technical person.
In such a case the syntax described in the camel users thread would be more intuitive in my
opinion :

       <from uri="direct://start"/>
       <to uri="book://addtoCatalog"/>

Best regards,


> Create a new blackbox component which can encapsulate routes using a specialized ProtocolBuilder
endpoint (similar to RouteBuilder)
> -----------------------------------------------------------------------------------------------------------------------------------
>                 Key: CAMEL-3285
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Ashwin Karpe
>            Assignee: Ashwin Karpe
>             Fix For: 2.6.0
>         Attachments:, routebox.diff
> Given below is the discussion forum thread that spawned this thought.
> Component requirements:
>  Need a Camel component (called Backbox, maybe) that can nicely expose a ProtocolBuilder
endpoint that does the following
>     a> Instantiate route definitions/route(s) configured in Spring or DSL at startup
>     b> Launch a Producer or Consumer with a well known protocol(s) so that a client
can invoke it (could be direct or seda initially but could be any protocol... really) . Must
support multiple consumer endpoints and routes using a URI scheme.
>     c> redirect received payloads (with marshalling into an exchange if necessary)
to the inner route(s) since they are launched and started. If there are multiple inner routes
with many consumers, we could expect the user to provide a clue using the payload and/or an
exchange property as to how the payload should be routed.
>     d> Extend from a Default Consumer, Producer, Endpoint and Component.
>     e> Internally manage inner route lifecycles and operations. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message