[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-nulable-arrays/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 from Spring Boot 2.4.3 to 3.5.10 introduces significant breaking changes. It requires a migration from Java 8 to Java 17, a shift from Java EE to Jakarta EE (renaming javax.* packages to jakarta.*), and brings in breaking changes from the underlying Spring Framework 6.x.

Highlights:

• Java 17 Baseline: Spring Boot 3.0 and higher require Java 17, so the project's JDK must be upgraded.
• Jakarta EE Migration: All javax.* package imports must be replaced with their jakarta.* equivalents. This is a major source-level breaking change affecting web-related APIs like javax.servlet to jakarta.servlet.
• WebFlux URL Matching: By default, trailing slashes in URL paths are no longer matched, which can lead to HTTP 404 errors for previously working endpoints.

Source: Spring Boot documentation
Recommendation: First, upgrade the project to the latest Spring Boot 2.7.x release. Then, upgrade to Java 17 and perform the javax to jakarta package migration. Finally, address the breaking changes in Spring Boot 3.x, paying close attention to URL matching behavior and updated configuration properties.

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