davsclaus commented on PR #21095: URL: https://github.com/apache/camel/pull/21095#issuecomment-3807234825
Beware the Exchange API is already big and its a central API for Camel end users. End users should use variables and not exchange properties. The latter is more for Camel internally and component developers and old school before variables was added to Camel. We have ExchangeHelper where extra methods is better suited that are not commonly in use, or would rarely need to be. So if you have some internal API cleanup where you want to remove those suppress warning then IMHO its not new methods on Exchange we should add, but on ExchangeHelper and then use that internally in Camel. -- 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]
