Fix: avoid PropertyResolver bean ambiguity with Sentinel#823
Open
98001yash wants to merge 1 commit intoapache:masterfrom
Open
Fix: avoid PropertyResolver bean ambiguity with Sentinel#82398001yash wants to merge 1 commit intoapache:masterfrom
98001yash wants to merge 1 commit intoapache:masterfrom
Conversation
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
1 participant
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.
This PR fixes an application startup failure caused by multiple
PropertyResolver beans being present when Dubbo is used together
with Sentinel.
The Dubbo auto-configuration previously exposed a generic
PropertyResolver bean, which conflicted with Spring's Environment.
This change narrows the exposed bean type to
DubboScanBasePackagesPropertyResolver, eliminating ambiguity and
aligning with Spring Boot auto-configuration best practices.
Fixes #727