-
Notifications
You must be signed in to change notification settings - Fork 728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Java 21 runtime] Java 21 runtime support for WSO2 Identity Server #21158
Comments
With the introduction of Java 21 LTS, most of the sun.java classes and methods are no longer supported. These internal APIs were never intended for public use and have been strongly encapsulated since Java 9. Continuing to rely on them in Java 21 poses significant risks, including potential runtime failures and compatibility issues. Therefore, it's essential to refactor the codebase to replace sun.java dependencies with standard, supported Java APIs to ensure long-term stability and maintainability of the product. Related PRs |
Some non-critical JDK internals, which are strongly encapsulated, are accessed via reflection for audit purposes. There are two approaches to address this:
The choice between these options should be made on a case-by-case basis. After evaluating backward compatibility, impact areas, and implementation complexity, we have opted for relaxed strong encapsulation for the following modules: For
Related PRs |
Java 17 runtime action for IS builder
Java 21 runtime action for IS builder |
|
Draft PRs until 7.1.0 is released |
|
This task is in the state of completed. Email reference "Review of JDK Compatibility Matrix for WSO2 Identity Server" |
|
Describe the issue:
The latest LTS release of Java; Java 21 was released on September 2023. As Identity Server is a downloadable product which will be used years after its releases, its important to plan for the latest LTS support for a upcoming release proactively.
This initiative aims to ensure compatibility with the Java 21 runtime for the IS product.
The text was updated successfully, but these errors were encountered: