[
https://issues.apache.org/jira/browse/CAMEL-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-3539:
-------------------------------
Description:
For example
{code:xml}
...
<to uri="route:sendMail"/>
...
{code}
And then we can have a route for that
{code:xml}
<route>
<from uri="route:sendMail"/>
...
</route>
{code}
In reality its just like a {{direct:}} endpoint but using {{route}} as scheme
name. And in this case the id of the route will use the name from the uri, so
it will name the route {{sendMail}}. Then you dont need to assign an explicit
id.
Now suppose the sendMail route also have another source input such as from a
jms queue
{code:xml}
<route id="sendMail>
<from uri="jms:queue:mail.out"/>
...
</route>
{code}
This route is now having the id {{sendMail}} which you can send message to
using the scheme {{route:sendMail}}.
But the route also consumes messages from a JMS queue.
was:
For example
{code:xml}
...
<to uri="route:sendMail"/>
...
{code}
And then we can have a route for that
{code:xml}
<route>
<from uri="route:sendMail"/>
...
</route>
{code}
In reality its just like a {{direct:}} endpoint but using {{route}} as scheme
name.
Now suppose the sendMail route also have another source input such as from a
jms queue
{code:xml}
<route id="sendMail>
<from uri="jms:queue:mail.out"/>
...
</route>
{code}
This route is now having the id {{sendMail}} which you can send message to
using the scheme {{route:sendMail}}.
But the route also consumes messages from a JMS queue.
> Add route endpoint to let end users send messages to other routes using route
> scheme naming
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-3539
> URL: https://issues.apache.org/jira/browse/CAMEL-3539
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.7.0, 3.0.0
>
>
> For example
> {code:xml}
> ...
> <to uri="route:sendMail"/>
> ...
> {code}
> And then we can have a route for that
> {code:xml}
> <route>
> <from uri="route:sendMail"/>
> ...
> </route>
> {code}
> In reality its just like a {{direct:}} endpoint but using {{route}} as scheme
> name. And in this case the id of the route will use the name from the uri, so
> it will name the route {{sendMail}}. Then you dont need to assign an explicit
> id.
> Now suppose the sendMail route also have another source input such as from a
> jms queue
> {code:xml}
> <route id="sendMail>
> <from uri="jms:queue:mail.out"/>
> ...
> </route>
> {code}
> This route is now having the id {{sendMail}} which you can send message to
> using the scheme {{route:sendMail}}.
> But the route also consumes messages from a JMS queue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
