-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8353232: Standardizing and Unifying XML Component Configurations #25102
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
Conversation
👋 Welcome back joehw! A progress list of the required criteria for merging this PR into |
@JoeWang-Java This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 6 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
@JoeWang-Java The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Joe,
This looks good overall.
/integrate |
Going to push as commit 66f0442.
Your commit was automatically rebased without conflicts. |
@JoeWang-Java Pushed as commit 66f0442. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This is a refactor patch, no change in functionality.
This patch refactor the configuration code. Rather than for each factory to go through the whole configuration process, a base configuration as represented in JdkXmlConfig is created once, which includes loading of the JAXP Configuration file, factories then get their own copies of the property managers, created on top of the base ones rather than directly constructed.
The JDKCatalog and its Resolver are lazily initialized when external references are encountered. This code replaces the original code block within the security manager. This change also addresses JDK-8350189.
The rest of changes basically replace all direct constructions of XMLSecurityManager/XMLSecurityPropertyManager with calls to JdkXmlConfig's corresponding get methods, which return clones of the base instances. in the factory classes, these clones are updated with property settings on the factories. In non-public or legacy code paths (inherited from upstream components), such updates may not be necessary.
Tests: existing tests T1-3 passed; XML JCK tests passed.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25102/head:pull/25102
$ git checkout pull/25102
Update a local copy of the PR:
$ git checkout pull/25102
$ git pull https://git.openjdk.org/jdk.git pull/25102/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25102
View PR using the GUI difftool:
$ git pr show -t 25102
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25102.diff
Using Webrev
Link to Webrev Comment