[Snyk] Security upgrade org.glassfish.jersey.media:jersey-media-json-jackson from 2.34 to 3.0.4

[pushkala-datastax]

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-18517159	710	org.glassfish.jersey.media:jersey-media-json-jackson: 2.34 -> 3.0.4 Major version upgrade No Path Found Proof of Concept

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[pushkala-datastax]

This major version upgrade from Jersey 2.x to 3.x introduces significant breaking changes, primarily due to the transition from Java EE to Jakarta EE 9.

Key Breaking Changes:

• Namespace Migration: The most critical change is the package namespace migration from javax.* to jakarta.*. All import statements for JAX-RS and related APIs in your application code must be updated. For example, javax.ws.rs.core must be changed to jakarta.ws.rs.core.
• Application Server Requirement: Jersey 3.x requires a Jakarta EE 9 compatible application server, such as Tomcat 10, Jetty 11, or GlassFish 6. It will not work on older servers compatible with Java EE 8.
• Removed Jackson 1 Support: Support for the outdated Jackson 1.x library has been completely removed. Your project uses jersey-media-json-jackson, so you must ensure you are using Jackson 2.x.
• Default Behavior Change: The property ServerProperties.UNWRAP_COMPLETION_STAGE_IN_WRITER_ENABLE is now enabled by default, which may alter the behavior of asynchronous responses.

Recommendation: This upgrade requires significant code and environment changes. Developers must perform a full migration of package imports from javax.* to jakarta.* and verify deployment on a compatible Jakarta EE 9 application server. Automated tools like OpenRewrite may assist with the namespace migration.

Source: Jersey 3.0 Migration Guide

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.