Hi That is not the intention, its a global option you set on the component level .. ideally. And if you have a single endpoint etc you can set it there.
You cannot have different started delayed, as its for starting the quartz scheduler On Mon, Apr 24, 2017 at 2:53 PM, dancerjohn <[email protected]> wrote: > I believe there is a bug in the QuartzComponent WRT startDelayedSeconds. I am > starting here instead of creating a ticket per the request on the forum. > This is how to demonstrate the issue: > > create route with start delay: > from("quartz2:route1?startDelaySeconds=25&trigger.repeatInterval=500").... > > create another route with NO start delay > from("quartz2:route2?trigger.repeatInterval=500").... > > Behavior is that route2 will have a start delay if it is created AFTER > route1 but NOT have a start delay if it is created BEFORE route1. This is > because the QuartzComponent is using a field for the startDelaySeconds and > not resetting it to null of the URI parameters to not have a > startDelaySeconds set. > > protected Endpoint More ...createEndpoint(String uri, String remaining, > Map<String, Object> parameters) throws Exception { > // Get couple of scheduler settings > Integer startDelayedSeconds = getAndRemoveParameter(parameters, > "startDelayedSeconds", Integer.class); > if (startDelayedSeconds != null) { > .............. this.startDelayedSeconds = > startDelayedSeconds; > > > So only if the variable "startDelayedSeconds" is not null will the > "this.startDelayedSeconds" be reset to the value desired by the URI. > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/QuartzComponent-startDelayedSeconds-bug-tp5798192.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
