[
https://issues.apache.org/activemq/browse/CAMEL-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-1556:
-------------------------------
Priority: Major (was: Minor)
Fix Version/s: 2.1.0
> Controlling initiatation order of routes
> ----------------------------------------
>
> Key: CAMEL-1556
> URL: https://issues.apache.org/activemq/browse/CAMEL-1556
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Henric Hedin
> Fix For: 2.1.0
>
>
> Would be nice if it was possible to control the order of how routes are
> initiated. If the following code is implemented within the same
> RouteBuilder.configure:
> // initiated from queue
> from("jms:queue:SOURCE_QUEUE").
> to("direct:processMsg");
> // initiated from file
> from("file://inbox).
> to("direct:processMsg");
> // Main flow
> from("direct:processMsg")
> .process("...")
> .to("validator:foo.xsd")
> .to("jms:queue:DEST_QUEUE");
> ... and there already is a message waiting on the JMS-source when camel is
> started, it could/will lead to the following error:
> WARN DirectProducer - No consumers available on endpoint:
> Endpoint[direct:processMsg] to process Exchange[JmsMessage:
> Today the are workarounds (by splitting in multiple files, and re-order
> route definitions), but maybe this could solved in some other better way
> (which also could affect a graceful shutdown).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
