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
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: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.