jiriOndrusek-agent commented on PR #28513: URL: https://github.com/apache/camel/pull/28513#issuecomment-6420239529
@oscerd > A *non-refusal* engine exception is fatal at startup [...] but, for a route added after start, is only logged [...] worth a word confirming it's intended Yes, intended, and not new in this PR. At startup the bridge publishes the registry snapshot from its own `doStart`, so an engine failure fails the start. A route added later reaches the bridge through the registry listener, and `AiToolRegistry` / `AiResourceRegistry` `notifyRegistered` log a failing listener without breaking the route's registration (by design since `CAMEL-24309`, mirrored for resources). Both paths behaved like this before; the PR only stops tracking a spec the engine failed to add. Unifying would either hide a broken engine at startup or change the registry listener contract, so I kept it. _Generated with [Claude Code](https://claude.com/claude-code) on behalf of @JiriOndrusek_ -- 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]
