camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] Commented: (CAMEL-2169) Support identifiers for Camel routes
Date Fri, 13 Nov 2009 11:50:52 GMT


Sergey Beryozkin commented on CAMEL-2169:

One more comment : it does not matter that Camel and JBI are diff components. This issue is
about letting Camel developers write routes without knowing the nitty-gritty details of container
environments, ex

in order to get a message from 

targetService="person:receiver" (see http:consumer)

a camel user should write

<camel:route id="{}endpoint">

it just does not make sense

> Support identifiers for Camel routes
> ------------------------------------
>                 Key: CAMEL-2169
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.2.0
>            Reporter: Sergey Beryozkin
>             Fix For: 2.2.0
> Camel routes embedded in camel contexts have no identifiers thus for a route to kick
in it has to start (in some cases at least) from a "from:" rule. Example from a route working
in SMX/JBI :
> <camel:camelContext>
> 	  <camel:route>
> 	     <camel:from uri="jbi:endpoint:"
>              <camel:to uri="jbi:endpoint:"
>           </camel:route>
> </camel:camelContext>
> The problem is that it makes a given route definition 'unportable' and requires a Camel
developer to know some cryptic details like the fully qualified name of the internal JBI endpoint.
> If I could do something like
> <camel:camelContext>
> 	  <camel:route id="{}endpoint">
>              <camel:to uri="jbi:endpoint:"
>           </camel:route>
> </camel:camelContext>
> then I'd be able to delegate to it easily from some other JBI endpoint, using targetService="person:endpoint"
> Likewise, camel routes could delegate to other routes :
> <camel:route id="{}endpoint">
>              <camel:to uri="route:"
> </camel:route>

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

View raw message