pudding0928 opened a new issue, #14661: URL: https://github.com/apache/dubbo/issues/14661
### Pre-check - [X] I am sure that all the content I provide is in English. ### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar issues. ### Apache Dubbo Component Java SPI Extensions (apache/dubbo-spi-extensions) ### Dubbo Version Dubbo Java 2.7.23,openJdk 1.11 ### Steps to reproduce this issue 1 CustomDispatcher implements Dispatcher and implements the related methods. 2 In the META-INF/dubbo directory, create a new file with the name org.apache.dubbo.remote.Dispatcher, with the content custom=com.xx.xx.CustomDispatcher 3 Call ProtocolConfig's setDispatcher method to set it to custom: protocolConfig.setDispatcher("custom") 4 start Provider sucessfully 5 When starting the consumer, it encounters the no provider error, and when tracing it through the debug, I found that when creating the NettyClient object, it calls org.apache.dubbo.remote.transport.dispatcher.ChannelHandlers#. wrapInternal -> ExtensionLoader.getExtensionLoader(Dispatcher.class) .getAdaptiveExtension() can't find the class CustomDispatcher and gives error PS: This error is not encountered when the Dispatcher's implementation class is changed to the built-in configuration. ### What you expected to happen The client-side Dispatcher should not be bound strictly and consistently to the server-side. If this is the case, there is no way to optimise the server-side Dispatcher schema when the client-side code is unable to make a task change that needs to be done ### Anything else _No response_ ### Are you willing to submit a pull request to fix on your own? - [ ] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
