[CAMEL-6461] camel-quartz - Stateful job - Redeploying bundle/war and having changed endpoint uri issue

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.10.4
• Fix Version/s: 2.10.7, 2.11.2, 2.12.0
• Component/s: camel-quartz
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 17/Jun/13 07:28
• Updated: 22/Jul/13 15:32
• Resolved: 22/Jul/13 15:32

Description

See
http://camel.465427.n5.nabble.com/In-came-quartz-route-after-bundle-update-jobs-are-not-triggred-tp5734196.html

In these situations we should use job.name to name the job unique so when you change the endpoint uri and redeploy the apps/bundles, then camel-quartz can find the old job in the quartz persistent store.

There may be logic needed to lookup using job.name as the unique name in these situations, and then allow endpoint uri options to change over time, such as the cron trigger etc. Which should be adjusted accordingly as well.