New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple @Reference annotations only have one effect #4674
Milestone
Comments
@mercyblitz Which @reference configuration can be use is depends on spring's load order, such as I have a default @reference and a custom @reference, I expect custom @reference work, but spring may load bean first which use default @reference,I think that is a problem |
The problem still exists. |
tswstarplanet
added a commit
to tswstarplanet/dubbo
that referenced
this issue
Aug 1, 2019
6 tasks
tswstarplanet
added a commit
to tswstarplanet/dubbo
that referenced
this issue
Aug 2, 2019
tswstarplanet
added a commit
to tswstarplanet/dubbo
that referenced
this issue
Aug 2, 2019
tswstarplanet
added a commit
to tswstarplanet/dubbo
that referenced
this issue
Aug 2, 2019
2 tasks
mercyblitz
added a commit
to mercyblitz/dubbo
that referenced
this issue
Sep 9, 2019
Merged
mercyblitz
added a commit
that referenced
this issue
Sep 23, 2019
mercyblitz
added a commit
that referenced
this issue
Feb 17, 2020
* Polish /#4687 : Remove the duplicated test code in dubbo-config-spring * Polish /#4674 & /#4470 * Polish /#5093 : Revert the previous commit * Polish #5093 : [Feature] Dubbo Services generate the metadata of REST services * Polish #5306 : [Migration] Upgrade the @SInCE tags in Javadoc migration cloud native to master * Polish #5306 : [Migration] Upgrade the @SInCE tags in Javadoc migration cloud native to master * Polish #5309 : [ISSURE] The beans of Dubbo's Config can't be found on the ReferenceBean's initialization * Polish #5312 : Resolve the demos' issues of zookeeper and nacos * Polish #5313 : [Migration] migrate the code in common module from cloud-native branch to master * Polish #5316 : [Refactor] Replace @EnableDubboConfigBinding Using spring-context-support * Polish #5317 : [Refactor] Refactor ReferenceAnnotationBeanPostProcessor using Alibaba spring-context-suuport API * Polish #5321 : Remove BeanFactoryUtils * Polish #5321 : Remove AnnotatedBeanDefinitionRegistryUtils * Polish #5321 : Remove AnnotationUtils * Polish #5321 : Remove ClassUtils * Polish #5321 : Remove BeanRegistrar * Polish #5321 : Remove ObjectUtils * Polish #5321 : Remove PropertySourcesUtils * Polish #5325 : [Migration] To migrate dubbo-metadata-api from cloud-native branch * Polish #5326 : [Migration] To migrate dubbo-metadata-processor from cloud-native branch * Polish #5329 : [Feature] To add the default metadata into ServiceInstance * Polish #5339 : [Refactor] Refactor the DynamicConfiguration interface * Polish bugfix * Fixes test cases * Merge remote-tracking branch 'upstream/master' into cloud-native-2.7.5 # Conflicts: # dubbo-configcenter/dubbo-configcenter-zookeeper/src/test/java/org/apache/dubbo/configcenter/support/zookeeper/ZookeeperDynamicConfigurationTest.java # dubbo-metadata/dubbo-metadata-api/src/test/java/org/apache/dubbo/metadata/DynamicConfigurationServiceNameMappingTest.java * Merge remote-tracking branch 'upstream/master' into cloud-native-2.7.5 # Conflicts: # dubbo-configcenter/dubbo-configcenter-zookeeper/src/test/java/org/apache/dubbo/configcenter/support/zookeeper/ZookeeperDynamicConfigurationTest.java # dubbo-metadata/dubbo-metadata-api/src/test/java/org/apache/dubbo/metadata/DynamicConfigurationServiceNameMappingTest.java * Polish /#5721 : [Enhancement] Setting the default IDs for Dubbo's Config Beans * Polish /#5729 : [Optimization] To remove EnableDubboConfigBinding and EnableDubboConfigBindings * Polish /#5594 : [Feature] Add the resolver of ServiceRestMetadata based on Java Reflection * Polish /#5736 : [Feature] Introducing Conversion features * Polish /#5737 : [Feature] Introducing "dubbo-metadata-processor" module * Polish /#5594 : Change the Metadata implementation * Polish /#5594 : Fixed test cases * Polish /#5594 : Fixed test cases * Polish /#5594 : Fixed test cases * Polish /#5594 : Fixed test cases * Polish /#5594 : Fixed test cases * Polish /#5594 : Fixed test cases * Polish /#5594 : Fixed test cases * Polish /#5594 : Fixed test cases
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Steps to reproduce this issue
Pls. provide [GitHub address] to reproduce this issue.
Expected Result
One bean is an asynchronous call and the other is a synchronous call
Actual Result
They are all asynchronous or synchronous
The text was updated successfully, but these errors were encountered: