camel-dev mailing list archives

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

    [ https://issues.apache.org/activemq/browse/CAMEL-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55395#action_55395
] 

Sergey Beryozkin commented on CAMEL-2169:
-----------------------------------------

I'm afraid you've missed my point. It is indeed in the hands on the SMX side and if this issue
has been fixed then it would simply let Camel users write the same route which will work in
SMX/standalone

> Support identifiers for Camel routes
> ------------------------------------
>
>                 Key: CAMEL-2169
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2169
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.2.0
>            Reporter: Sergey Beryozkin
>
> 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:http://servicemix.apache.org/samples/wsdl-first/receiver/endpoint"
/>
>              <camel:to uri="jbi:endpoint:http://servicemix.apache.org/samples/wsdl-first/staticlistener/staticendpoint"
/>
>           </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="{http://servicemix.apache.org/samples/wsdl-first/receiver}endpoint">
>              <camel:to uri="jbi:endpoint:http://servicemix.apache.org/samples/wsdl-first/staticlistener/staticendpoint"
/>
>           </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="{http://servicemix.apache.org/samples/wsdl-first/receiver}endpoint">
>              <camel:to uri="route:http://servicemix.apache.org/samples/wsdl-first/staticlistener/staticendpoint"
/>
> </camel:route>

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


Mime
View raw message