prasanthrao opened a new pull request, #24670:
URL: https://github.com/apache/camel/pull/24670
# Description
`QuartzEndpoint` registered every custom calendar under the same hardcoded
scheduler name
`"CamelQuartzCustomCalendar"`. When two or more routes in the same
`CamelContext` each configured
a `customCalendar`, the second `addCalendar(..., replace=true)` call
silently overwrote the first.
All triggers were wired to that same name via `modifiedByCalendar(...)`,
so every trigger ended up
governed by whichever calendar registered last — not the one intended for
it.
**Fix:** replace the hardcoded constant with a per-endpoint name derived
from the trigger key:
CamelQuartzCustomCalendar_<group>_<name>
The trigger key is always set by `QuartzComponent` before the endpoint
starts, is stable across
restarts (same URI → same trigger key), and is already guaranteed unique
within the scheduler.
A new regression test (`QuartzCustomCalendarCollisionTest`) verifies that
two routes with different
custom calendars each register and retain their own independent calendar
entry.
# Target
- [x] I checked that the commit is targeting the correct branch (Camel 4
uses the `main` branch)
# Tracking
- [x] If this is a large change, bug fix, or code improvement, I checked
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL-24055)
filed for the change (usually before you start working on it).
# Apache Camel coding standards and style
- [x] I checked that each commit in the pull request has a meaningful
subject line and body.
- [x] I have run `mvn clean install -DskipTests` locally from root folder
and I have committed all auto-generated changes.
# AI-assisted contributions
- [x] If this PR includes AI-generated code, commits have proper
co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR
description identifies the AI tool used.
_Claude Code on behalf of Prasanth Rao_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
