Ranx, the timeouts can change even for the same resource. The main idea
behind this approach is to be able to use a Resource in different workflows,
so, the available time allowed per operation can change in function of the
process that is being performed.
I'm setting up the routes using REST DSL and redirecting them to seda and
creating a new route from seda (using the generated id) to a Bean with the
implented class.
I understand that you're solution is to use a dynamic route using the
recipientList, something like:
from the actual approach
.to("seda:"+id+"?timeout=1000");
to something like
.recipientList(simple("seda:"+id+"?timeout=${header.timeout}")) ?
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-SEDA-timeout-Update-it-at-runtime-tp5786538p5786564.html
Sent from the Camel - Users mailing list archive at Nabble.com.
