[Snyk] Security upgrade org.springframework.boot:spring-boot-starter-webflux from 2.4.3 to 3.5.10

[ayusuf-mq]

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

Snyk changed the following file(s):

• samples/client/petstore/java/webclient/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	External Initialization of Trusted Variables or Data Stores SNYK-JAVA-CHQOSLOGBACK-15062482	290	org.springframework.boot:spring-boot-starter-webflux: 2.4.3 -> 3.5.10 Major version upgrade No Path Found No Known Exploit

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[ayusuf-mq]

This major version upgrade introduces significant breaking changes, requiring a migration to Java 17 and a complete transition from Java EE to Jakarta EE, which will necessitate code and dependency updates.

Highlights:

• Java 17 Required: The runtime environment must be upgraded to Java 17, as older versions are no longer supported.
• Jakarta EE Namespace Migration: All javax.* package imports must be replaced with jakarta.*. This is a major breaking change affecting all APIs that depend on specifications like Servlet or JPA.
• WebFlux URL Matching: By default, trailing slashes in URLs are no longer matched. For example, a request to /endpoint/ will not match a @GetMapping(\"/endpoint\").

Source: Spring Boot documentation
Recommendation: Plan for a multi-step migration. First, ensure the application is on the latest Spring Boot 2.7 release. Then, upgrade to Java 17 and begin the migration to Spring Boot 3, using tools like OpenRewrite or IDE features to assist with the javax to jakarta package rename. Add the spring-boot-properties-migrator dependency to help identify changed configuration properties.

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