Add service provider discovery for time zone providers - #834
Open
bokken wants to merge 1 commit into
Open
Conversation
Allow DateTimeZone Provider and NameProvider implementations to be discovered from META-INF/services files System-property providers retain priority and fail strictly when invalid. SPI providers are tried in discovery order, with unusable implementations skipped before falling back to the existing defaults.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughThis change adds service-provider discovery for ChangesService-provider loading
Estimated code review effort: 4 (Complex) | ~50 minutes Sequence Diagram(s)sequenceDiagram
participant DateTimeZone
participant ServiceProviderLoader
participant ClassLoader
participant BuiltInProvider
DateTimeZone->>ServiceProviderLoader: load Provider or NameProvider
alt system property is set
ServiceProviderLoader->>ClassLoader: load configured class
ClassLoader-->>ServiceProviderLoader: provider instance or error
ServiceProviderLoader-->>DateTimeZone: validated provider or RuntimeException
else system property is not set
ServiceProviderLoader->>ClassLoader: scan META-INF/services
ClassLoader-->>ServiceProviderLoader: declared provider classes
ServiceProviderLoader-->>DateTimeZone: first valid discovered provider or null
alt no valid discovered provider
DateTimeZone->>BuiltInProvider: use built-in fallback
BuiltInProvider-->>DateTimeZone: default provider
end
end
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allow DateTimeZone Provider and NameProvider implementations to be discovered from META-INF/services files
System-property providers retain priority and fail strictly when invalid.
SPI providers are tried in discovery order, with unusable implementations skipped before falling back to the existing defaults.
The goal is to make it easier to leverage the JDK provide ZoneRules (as described here #491) with assembly management only.
Summary by CodeRabbit
New Features
Bug Fixes
Documentation