[
https://issues.apache.org/activemq/browse/CAMEL-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55400#action_55400
]
Sergey Beryozkin commented on CAMEL-2169:
-----------------------------------------
Hi Claus
> <camel:route
> id="{http://servicemix.apache.org/samples/wsdl-first/receiver}endpoint";>
it was a typo which I pointed out to in the follow-up comment.
Basically, here is the thing. I've tried to write a Camel route as part of the
internal project. I found it unnatural that I had to start a camel route in SMX
from a "from:" route. None of the other SMX components requires that an
endpoint which might be targeted by some higher-level endpoint needs to know
about that higher-level endpoint.
Also I know that some composite routes like a static-recipients one, certainly
does not have to start "from:"
It's not that is blocking me and happy to forget this issue for good. This
issue is about making it easy to write a Camel route so that it can be easily
included in other higher-level routing environments.
Consider a super complex route (using log: just for brewity.)
<camel:camelContext>
<camel:to uri="log:test" />
</camel:route>
</camel:camelContext>
I have a requirement now : reuse in SMX and Mule. So rather than have a camel
component added to Camel for integrating with every other container environment
out there I'd probably just implement a Mule adapter which would delegate from
Mule routes to my camel route
But as I said - I'm ok with putting this issue to bed
thanks
> 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.
