Migration of QPP-NG from v4.2.2 to v4.3.0

Dependency Upgrades

As part of this release, we’ve upgraded several key dependencies to modern versions to improve performance, security, and compatibility. Below are the details of the upgrades and their impact: 

Upgraded Dependencies

Dependency 

Previous Version 

Upgraded Version 

Java 

8 

21 

Spring Boot 

2.x 

3.4.2 

Spring Framework 

5.x 

6.2.0 

Tomcat 

9.x 

10.1.34 

Spring Security 

5.x 

6.4.0 

Spring Cloud 

2021.0.3 

2024.0.0 

Spring Cloud Azure 

4.19.0 

5.19.0 

AWS Java SDK Core 

1.12.759 

1.12.780 

AWS Secrets Manager JDBC 

1.0.11 

2.0.2 

Keycloak 

22.x 

26.1.1 

Key Changes & Migration Considerations

  1. Migration from javax to Jakarta EE 

    • The project now incorporates the Jakarta Servlet dependency to support this transition. 

    • Code referencing javax.servlet needs to be updated to jakarta.servlet. 

  2. Spring Boot & Spring Framework Upgrades 

    • Spring Boot 3.x and Spring Framework 6.x introduce breaking changes, requiring code and configuration updates. 

    • Deprecated APIs in previous versions may no longer be available. 

  3. Security Configuration Updates 

    • Adjustments were made to align with Spring Security 6.x, which enforces stricter authentication and authorization policies. 

    • Certain WebSecurityConfigurerAdapter implementations may need to be refactored using the new SecurityFilterChain approach. 

  4. Tomcat Upgrade to 10.x 

    • The shift from Tomcat 9.x to 10.1.34 aligns with Jakarta EE and requires application configurations to reflect the new API changes. 

  5. Refactored Project Structure 

    • Remoting stubs and interfaces have been moved to a separate project to ensure compatibility with older versions of Java and Spring Boot. 

    • If your application relies on these components, adjustments may be required in dependency management. 

Please note that Spring Feign Clients haven't yet been upgraded to Java 21. To minimize the impact on custom implementations, we recommend migrating all custom implementations to the latest technology stack. This will ensure a smoother transition, as we plan to upgrade the Feign Clients to Java 21 in the near future. 

Recommended Action 

  • Update project dependencies and resolve compatibility issues in custom implementations. 

  • Review and update any references to Javax packages. 

  • Modify security configurations as per the new Spring Security standards. 

  • Test and validate all functionality to ensure a smooth transition.