squakez commented on issue #3560: URL: https://github.com/apache/camel-k/issues/3560#issuecomment-1230042204
> @lburgazzoli you're right. I was mislead by [this commit where you fixed some log comment](https://github.com/apache/camel-k-runtime/commit/e199b358000459dd8eff5efa1bd9c6eb60eced63) only. After all, my memory is not in that bad shape... I dug a bit more and indeed there was [some change in the Error Handler managment in Camel 3.17](https://github.com/apache/camel/commit/870e656bd6cf67a6e46ee3419b67ada860386d70#diff-f5f5e129daa69bcc30b62eac7c3ef1dffd748c1da3637d9c9d724d3ce8a316cc). This one introduced a regression on Camel K runtime, as [one supporting method was wiped off](https://github.com/apache/camel/pull/5315). In order to fix this, we'll probably need to reintroduce [a workaround we had in place for pre 3.10 Camel releases](https://github.com/apache/camel-k-runtime/commit/c1186b92a027c2a5b2723fa3a2dd9352c9a562a2). Without that check, there is no way we can verify if a default error handler, as the `getErrorHandlerFactory()` is in charge to create one, when it is called. I'll test it locally to see if it works and report how it goes. fyi @davsclaus -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
