Of course that's what happens. If you send it to stream:out (if it works
you probably added a dependency on camel-stream) it will use a Producer
to send it to std:out (as that is the behavior of camel-stream with a
stream:out uri).
If you send it to direct:start, the behavior of the direct component
(from camel-core) is to send it to a Consumer with the same uri. But you
don't have such a consumer. The expectation is to have a route that has
a <from uri="direct:start" /> (using the xml dsl). You either don't have
that (because you changed the uri in the properties or context.xml file)
or the route doesn't auto-start.
Hadrian
On 11/21/2011 04:30 PM, newbiee wrote:
I have following route:
<route id="ping-digi">
<from uri="jms:digiQueue" />
<setHeader
headerName="DigiId"><simple>${body}</simple></setHeader>
<setHeader
headerName="DigiUri"><simple>netty:tcp://${body}?sync=true</simple></setHeader>
<setBody><header>DigiUri</header></setBody>
<to uri="direct:start" />
<routingSlip><header>DigiUri</header></routingSlip>
</route>
If I replace:
<to uri="direct:start" />
<routingSlip><header>DigiUri</header></routingSlip>
with:
<to uri="stream:out"/>
The value of "DigiUri" is printed on the command prompt.
But with the above route I am getting following error:
WARN No consumers available on endpoint: Endpoint[direct://start] to
process: Exchange ...........
Please help me fixing this error.
Thank you
--
View this message in context:
http://camel.465427.n5.nabble.com/No-consumers-available-on-endpoint-Endpoint-direct-start-tp5011742p5011742.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/
