You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Hadrian Zbarcea (JIRA)" <ji...@apache.org> on 2010/08/31 03:59:40 UTC
[jira] Created: (CAMEL-3091) QuartzEndpoint does not set the job
name properly
QuartzEndpoint does not set the job name properly
-------------------------------------------------
Key: CAMEL-3091
URL: https://issues.apache.org/activemq/browse/CAMEL-3091
Project: Apache Camel
Issue Type: Bug
Components: camel-quartz
Affects Versions: 2.4.0
Reporter: Hadrian Zbarcea
Assignee: Hadrian Zbarcea
Fix For: 2.5.0
Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:uri"}} vs {{"quartz://"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-3091) QuartzEndpoint does not set the job
name properly
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61538#action_61538 ]
Hadrian Zbarcea commented on CAMEL-3091:
----------------------------------------
Added failing test in {{QuartzEndpointConfigureTest}} that shows the problem.
> QuartzEndpoint does not set the job name properly
> -------------------------------------------------
>
> Key: CAMEL-3091
> URL: https://issues.apache.org/activemq/browse/CAMEL-3091
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-quartz
> Affects Versions: 2.4.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.5.0
>
>
> Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
> Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:<uri>"}} vs {{"quartz://<uri>"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-3091) QuartzEndpoint does not set the job
name properly
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61535#action_61535 ]
Hadrian Zbarcea commented on CAMEL-3091:
----------------------------------------
The job name part is resolved in r991060.
> QuartzEndpoint does not set the job name properly
> -------------------------------------------------
>
> Key: CAMEL-3091
> URL: https://issues.apache.org/activemq/browse/CAMEL-3091
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-quartz
> Affects Versions: 2.4.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.5.0
>
>
> Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
> Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:<uri>"}} vs {{"quartz://<uri>"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-3091) QuartzEndpoint does not set the job
name properly
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated CAMEL-3091:
-----------------------------------
Description:
Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:<uri>"}} vs {{"quartz://<uri>"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
See {{nabble thread|http://camel.465427.n5.nabble.com/Problem-with-cron-expression-configuration-in-camel-context-with-spring-tt2796958.html#a2796958}}. Many thanks to SK for reporting this.
was:
Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:<uri>"}} vs {{"quartz://<uri>"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
> QuartzEndpoint does not set the job name properly
> -------------------------------------------------
>
> Key: CAMEL-3091
> URL: https://issues.apache.org/activemq/browse/CAMEL-3091
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-quartz
> Affects Versions: 2.4.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.5.0
>
>
> Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
> Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:<uri>"}} vs {{"quartz://<uri>"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
> See {{nabble thread|http://camel.465427.n5.nabble.com/Problem-with-cron-expression-configuration-in-camel-context-with-spring-tt2796958.html#a2796958}}. Many thanks to SK for reporting this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-3091) QuartzEndpoint does not set the job
name properly
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated CAMEL-3091:
-----------------------------------
Description:
Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:<uri>"}} vs {{"quartz://<uri>"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
was:
Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:uri"}} vs {{"quartz://"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
> QuartzEndpoint does not set the job name properly
> -------------------------------------------------
>
> Key: CAMEL-3091
> URL: https://issues.apache.org/activemq/browse/CAMEL-3091
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-quartz
> Affects Versions: 2.4.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.5.0
>
>
> Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
> Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:<uri>"}} vs {{"quartz://<uri>"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-3091) QuartzEndpoint does not set the job
name properly
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated CAMEL-3091:
-----------------------------------
Description:
Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:<uri>"}} vs {{"quartz://<uri>"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
See [nabble thread|http://camel.465427.n5.nabble.com/Problem-with-cron-expression-configuration-in-camel-context-with-spring-tt2796958.html#a2796958]. Many thanks to SK for reporting this.
was:
Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:<uri>"}} vs {{"quartz://<uri>"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
See {{nabble thread|http://camel.465427.n5.nabble.com/Problem-with-cron-expression-configuration-in-camel-context-with-spring-tt2796958.html#a2796958}}. Many thanks to SK for reporting this.
> QuartzEndpoint does not set the job name properly
> -------------------------------------------------
>
> Key: CAMEL-3091
> URL: https://issues.apache.org/activemq/browse/CAMEL-3091
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-quartz
> Affects Versions: 2.4.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.5.0
>
>
> Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
> Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:<uri>"}} vs {{"quartz://<uri>"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
> See [nabble thread|http://camel.465427.n5.nabble.com/Problem-with-cron-expression-configuration-in-camel-context-with-spring-tt2796958.html#a2796958]. Many thanks to SK for reporting this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-3091) QuartzEndpoint does not set the job
name properly
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-3091.
--------------------------------
Resolution: Fixed
> QuartzEndpoint does not set the job name properly
> -------------------------------------------------
>
> Key: CAMEL-3091
> URL: https://issues.apache.org/activemq/browse/CAMEL-3091
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-quartz
> Affects Versions: 2.4.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.5.0
>
>
> Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
> Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:<uri>"}} vs {{"quartz://<uri>"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
> See [nabble thread|http://camel.465427.n5.nabble.com/Problem-with-cron-expression-configuration-in-camel-context-with-spring-tt2796958.html#a2796958]. Many thanks to SK for reporting this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-3091) QuartzEndpoint does not set the job
name properly
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61552#action_61552 ]
Claus Ibsen commented on CAMEL-3091:
------------------------------------
trunk: 991189.
Fixed the parameter parsing bug in camel-core due the ? mark in the cron expression
> QuartzEndpoint does not set the job name properly
> -------------------------------------------------
>
> Key: CAMEL-3091
> URL: https://issues.apache.org/activemq/browse/CAMEL-3091
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-quartz
> Affects Versions: 2.4.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.5.0
>
>
> Looks like the job.name argument is not se properly on the endpoint and defaults to the uri path.
> Another nastier issue (for which I should have probably created a separate issue) is that the uri gets messed up if it does not have the double slashes after the scheme (as in {{"quartz:<uri>"}} vs {{"quartz://<uri>"}}) and the @cron argument contains '?'. The workaround (arguably) is to start the uri with {{"quartz://..."}}.
> See [nabble thread|http://camel.465427.n5.nabble.com/Problem-with-cron-expression-configuration-in-camel-context-with-spring-tt2796958.html#a2796958]. Many thanks to SK for reporting this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.