[Snyk] Security upgrade org.springframework:spring-context from 5.3.19 to 7.0.9

[chrislin22]

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-ORGSPRINGFRAMEWORK-19267075	701	org.springframework:spring-context: 5.3.19 -> 7.0.9 Major version upgrade No Known Exploit

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

[chrislin22]

This is a major upgrade across two full versions (5.x → 6.x → 7.x) and introduces significant breaking changes that require mandatory code and environment modifications. This is a large-scale migration effort, not a routine dependency update.

Key Breaking Changes for 5.3 → 6.0:

• Java 17 Baseline: Spring Framework 6.0 requires Java 17 as the minimum version. [5, 16, 18]
• Jakarta EE 9 Migration: This is the most impactful change. Spring 6 migrates from Java EE to Jakarta EE 9. All javax.* package imports for specifications like Servlet, JPA, and Bean Validation must be refactored to the jakarta.* namespace (e.g., javax.servlet.http.HttpServletRequest becomes jakarta.servlet.http.HttpServletRequest). [5, 11]
• Dependency Upgrades: This migration necessitates upgrading related dependencies, such as moving to Tomcat 10+/Jetty 11+ and Hibernate ORM 6.1+. [11, 18]
• Removed APIs: Support for several older integrations has been removed, including Commons FileUpload, Tiles, and Ehcache 2.x. [11, 18]

Key Breaking Changes for 6.x → 7.0:

• Jakarta EE 11 Baseline: Spring Framework 7.0 raises the baseline to Jakarta EE 11. [1, 2, 15]
• javax.annotation Becomes Ineffective: Annotations from javax.annotation and javax.inject (e.g., @PostConstruct, @PreDestroy, @Resource) are ignored at runtime. They will compile but not be processed by Spring, leading to silent failures. They must be replaced with their `jakarta.annotation

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