davsclaus commented on PR #15515: URL: https://github.com/apache/camel/pull/15515#issuecomment-2343436927
> @davsclaus I agree that it should be fixed in Jackson. Sadly, it hasn't been fixed for a long time and they don't consider it much of an issue. This _hack_ as you call it just tries to overcome the error by invoking different string-writing mechanism (on their side) and things should be same as soon as calling Jackson _marshal_ method ends. > > I see no point in providing an option. It's hardly an option for Camel users. It's either fixed, or not. > I am sorry but we cannot risk affecting everyone else with some code change that Jackson itself does have out of the box, and its been outstanding since 2015. Would such a change cause unforseen changes to existing users, performance degration or what else. Are there other reported tickets at Jackson than this single instance? > > Also we need unit tests to go with that thanks. > > It cannot be unit-tested. It's integration issue. > What we ask is that there is a junit test class in the PR that tests this code change. > If you don't want this fix (which I can understand), feel free to close it. I'll then try to create a fix for Jackson itself. But I doubt they will accept it... Maybe take more time to investigate if there are other reports on Jackson. But in the mean time there is only a solution you can do and that is on the Camel side. But that requires more work which you then must step up and do. And it would require a JIRA ticket in the Apache Camel JIRA at https://issues.apache.org/jira/projects/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]
