You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
privateURLoverrideWithConfigurator(URLproviderUrl) {
// override url with configurator from "override://" URL for dubbo 2.6 and beforeproviderUrl = overrideWithConfigurators(this.configurators, providerUrl);
// override url with configurator from configurator from "app-name.configurators"providerUrl = overrideWithConfigurators(CONSUMER_CONFIGURATION_LISTENER.getConfigurators(), providerUrl);
// override url with configurator from configurators from "service-name.configurators"if (serviceConfigurationListener != null) {
providerUrl = overrideWithConfigurators(serviceConfigurationListener.getConfigurators(), providerUrl);
}
returnproviderUrl;
}
Pls. provide [GitHub address] to reproduce this issue.
Expected Result
What do you expected from the above steps?
Actual Result
What actually happens?
If there is an exception, please attach the exception trace:
Just put your stack trace here!
The text was updated successfully, but these errors were encountered:
Environment
Steps to reproduce this issue
�the override rule logic is different between Provider and Consumer.
Provider check ProviderConfigurationListener and then the ServiceConfigurationListener,
Consumer check ConsumerConfigurationListener and then the ReferenceConfigurationListener
i think we should keep them consistent and ServiceConfigurationListener should override ProviderConfigurationListener.
provider:
org.apache.dubbo.registry.integration.RegistryProtocol.OverrideListener#doOverrideIfNecessary
consumer:
org.apache.dubbo.registry.integration.RegistryDirectory#overrideWithConfigurator
Pls. provide [GitHub address] to reproduce this issue.
Expected Result
What do you expected from the above steps?
Actual Result
What actually happens?
If there is an exception, please attach the exception trace:
The text was updated successfully, but these errors were encountered: