Hi Vishal,
routeB doesn't seem correct to me. At the end of the route, you are
calling again the same route: to("direct:routeB")
Any reason for that?
Bilgin
On 4 December 2012 07:25, vishalad <adsule.vis...@gmail.com> wrote:
> Hi All,
>
> I have a route A which is timer based route and gets invoke at server
> startup. In this route, I am calling another route B which does some
> processing and put the response in exchange body.
>
> public class A extends RouteBuilder{
> @Override
> public void configure() throws Exception {
> from("timer://myTimer?repeatCount=1&delay=1000")
> .startupOrder(1)
> .process(new Processor() {
> @Override
> public void process(Exchange exchange) throws
> Exception {
> exchange.getIn().setBody("Hello", String.class);
> }
> })
>
> .to("direct:routeB")
> }
> }
>
> public class B extends RouteBuilder{
> @Override
> public void configure() throws Exception {
>
> from("direct:routeB")
> .process(new Processor() {
> @Override
> public void process(Exchange exchange) throws
> Exception {
> exchange.getIn().setBody("Hello route B",
> String.class);
> }
> })
>
> .to("direct:routeB")
> }
> }
>
> When i start my app sever, route A gets loaded at the time of loading the
> camel context but i am getting the error message as No consumer available
> for endpoint direct:routeB.
>
> Does anyone know why this is happening and any work around for this.
>
> Any help would be appreciated.
>
> .....Vishal.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/No-consumers-available-for-endpoint-tp5723587.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
