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 (I also added a failing test to the trunk).
Thanks for reporting this!
Hadrian
On Aug 30, 2010, at 10:24 PM, senthil.arumugam wrote:
>
> 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.
>
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
> resolve endpoint: quartz://mailer/ticketTimer?%2B*%2B1-7 due to: There are 1
> parameters that couldn't be set on the endpoint. Check the uri if the
> parameters are spelt correctly and that they are properties of the endpoint.
> Unknown parameters=[{%2B*%2B1-7=null}]
> at
> org.apache.camel.impl.DefaultComponent.validateParameters(DefaultComponent.java:126)
> at
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:89)
> at
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:370)
> ... 32 more
>
> -SK
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Problem-with-cron-expression-configuration-in-camel-context-with-spring-tp2796958p2797558.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
