Skip to content

Add Jackson 3 support and deprecate Jackson 2 APIs #10058

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
artembilan opened this issue May 28, 2025 · 9 comments
Open

Add Jackson 3 support and deprecate Jackson 2 APIs #10058

artembilan opened this issue May 28, 2025 · 9 comments

Comments

@artembilan
Copy link
Member

This is where we use it:

  • ConfigurableCompositeMessageConverter
  • WebSocketInboundChannelAdapter
  • WebSocketOutboundMessageHandler
  • StompInboundChannelAdapterWebSocketIntegrationTests

Has to be migrated to a new JacksonJsonMessageConverter.

@artembilan artembilan added this to the 7.0.0-M1 milestone May 28, 2025
@anthologia
Copy link
Contributor

Hi! Would it be okay if I work on this issue?

Is this related to spring-projects/spring-framework#33798?

@artembilan
Copy link
Member Author

That's correct.
Feel free to open Pull Request.
However we need to be careful if this has to be done before: spring-projects/spring-framework#34963.

@artembilan
Copy link
Member Author

Repurpose an issue to a broader subject.
Essentially, we have to provide Jackson 3 support and deprecate existing Jackson 2 API.
More info in: spring-projects/spring-framework#33798

@artembilan artembilan changed the title Mitigate a deprecation of MappingJackson2MessageConverter from Spring Framework 7.0 Add Jackson 3 support and deprecate Jackson 2 APIs Jun 6, 2025
@anthologia
Copy link
Contributor

Hi @artembilan!

I see the scope got expanded. Are we looking at migrating Jackson 2 to 3 across all Spring Integration modules for this issue?

@artembilan
Copy link
Member Author

Thank you for looking into this, @anthologia !

Well, it is not about migration any more.
We have to add Jackson 3 dependency, implement Jackson 3 mirrored API where we Jackson 2 and deprecate those Jackson 2 API.
In between we can migrate to a new JacksonJsonMessageConverter where we see deprecation warnings for the MappingJackson2MessageConverter.

The most important part that Jackson 3 has to be managed as dependency to make everything working.

@anthologia
Copy link
Contributor

Thanks for clarifying! I'll fix the compile warning issues (in this milestone) first, then get into this.

@artembilan
Copy link
Member Author

I'll fix the compile warning issues

Thanks.
I hope you mean warnings related to this issue, not many others like JUnit 4 deprecations, or this-espace because of Java 24 upgrade.

@anthologia
Copy link
Contributor

Oh, I meant I'd handle the this-escape warnings in #10069 first, then come back to this Jackson issue. I've already started on the this-escape issue. I wasn't planning to mix them together..!

@artembilan
Copy link
Member Author

Good.
Would be great if you would comment on that issue that you are working on it.
This way anyone interested would not do the same effort 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants