Yeah, it's a parameter parsing and url normalizing issue, I'll have to look
into.
But you are correct, that is the wrong, unexpected but consistent and
predictable outcome of not having the double slashes.
Not nice, I know but it's easy to avoid it. Watch the CAMEL-3091 issue for more
details (
The job name is properly set now (see
https://issues.apache.org/activemq/browse/CAMEL-3091) and if not set it
defaults to "quartz-{endpoint.getId()}".
The rest should work and I'll try get the double slash issue resolved. It's not
a big deal, but components should behave consistently wether the
Hi Hadrian,
Thanks for your quick response.
When I use like how you suggested and I got it working fine, Thank you.
But I would like to know the significance in using '//' after quartz. If I
don't use it, I am getting the following exception. It occurs when I use '?'
in the cron expression.
Ca
Hi,
Try this:
uri="quartz://sample/trigger1?job.name=sampleJob&cron=0+0/5+*+?+*+1-7"
or even:
uri="quartz://sample/trigger1?cron=0+0/5+*+?+*+1-7"
Note the double slashes after "quartz:" and the spaces replaced with '+'.
it seems to me that the job name is not set properly anyway, and I am looking
