Repository navigation
MCR-3703 Parse configuration properties into tree structure eagerly #3075
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
Open
toKrause
wants to merge
4
commits into
main
Choose a base branch
from
issues/MCR-3703_Parse-configuration-properties-into-tree-structure-eagerly
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
9af3697
MCR-3703 ! parse configuration properties into tree structure eagerly
toKrause fdcb980
MCR-3703 fix minor issues
toKrause 9ad87e1
MCR-3703 properly support uncommon properties
toKrause a98e735
MCR-3703 add explicit empty implementation, exclude class and sentina…
toKrause File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
50 changes: 50 additions & 0 deletions
50
mycore-base/src/main/java/org/mycore/common/config/instantiator/MCREmptyTree.java
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,50 @@ | ||
| package org.mycore.common.config.instantiator; | ||
|
|
||
| import java.util.Map; | ||
| import java.util.stream.Stream; | ||
|
|
||
| import org.mycore.common.log.MCRTreeMessage; | ||
|
|
||
| public class MCREmptyTree implements MCRProperTree { | ||
|
|
||
| @Override | ||
| public String value() { | ||
| return ""; | ||
| } | ||
|
|
||
| @Override | ||
| public Stream<String> keys() { | ||
| return Stream.empty(); | ||
| } | ||
|
|
||
| @Override | ||
| public MCRProperTree nested(String key) { | ||
| return MCRPropertiesTree.EMPTY; | ||
| } | ||
|
|
||
| @Override | ||
| public MCRProperTree deeplyNested(String key) { | ||
| return MCRPropertiesTree.EMPTY; | ||
| } | ||
|
|
||
| @Override | ||
| public MCRProperTree excludeKey(String classKey) { | ||
| return this; | ||
| } | ||
|
|
||
| @Override | ||
| public Map<String, String> toProperties() { | ||
| return Map.of(); | ||
| } | ||
|
|
||
| @Override | ||
| public MCRTreeMessage toTreeMessage() { | ||
| return new MCRTreeMessage(); | ||
| } | ||
|
|
||
| @Override | ||
| public String toString() { | ||
| return "{ }"; | ||
| } | ||
|
|
||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
With the
CONFIGURATIONScache gone, everygetInstanceOf/getSingleInstanceOfcall runsresolveValueClassand thusMCRClassTools.forNameagain, even if the singleton is already ininstanceHolder. For classes from plugin JARs inmycore-home/lib,Class.forNamefirst throws aClassNotFoundExceptionon every call before theextendedClassLoaderis tried. The cache was explicitly reintroduced in MCR-3668 (7d9a135). Is dropping it intended, or should the resolved configuration (or at least the value class) still be cached?