Maybe our original intention is different. I assume a scene: when I accidentally customize a dubbo internal filter（just the same name） in another framework, when user use these two jars(our framework & dubbo), how can you guarantee who is loaded first. According to dubbo currently, the first filter loaded will enter the filter chain, and the later loaded same name filter will throw an exception, but this exception is eaten, how do you notify the user. At least we have encountered this situation in Win10 and Centos7, and there is no exception, but the filter does not work.
[ Full content available at: https://github.com/apache/dubbo/pull/4365 ] This message was relayed via gitbox.apache.org for [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
