EventSourceNotFoundException.javaEventManager cannot locate an event source by its UUID. This is the first-tier exception in the two-tier lookup failure hierarchy. It occurs when a FullCalendar Ajax callback contains a source UUID that doesn't match any of the calendar's configured event sources — typically indicating a stale client state (e.g., an event source was removed server-side but the client's cached configuration still references it), or a client-side error sending a corrupted UUID. Extends RuntimeException for seamless integration with Wicket's Ajax callback exception handling.This exception and EventNotFoundException (file #2782) form a distinguished failure hierarchy rather than using a single generic exception with an error code. The distinction allows handlers to implement different recovery strategies: for a missing source, the handler might remove the source's events from the client; for a missing event, it might revert the specific event to its previous position. Both are siblings extending RuntimeException directly, rather than one subclassing the other, reflecting that they represent failures at different levels of the lookup chain.
The constructor receives a message formatted as "Event source with uuid: {uuid} not found", which is useful for server-side logs. The UUID value helps operators diagnose whether the issue is a stale session (old UUID from a previous page render) or a malformed client request.
| Commit | What changed |
|---|---|
868d6abb7 through ceb63e8a1 | Six annual copyright header updates. The exception class remains in its original form — the single-constructor, message-only design fulfills all diagnostic and recovery needs for source lookup failures. |