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
If Service bean annotated Dubbo @Service and Spring @Service and @ComponentScan executes earlier than @DubboComponentScan , current been will not be a candidate of @Service Bean.
@DubboComponentScan should consider this scenario:
There are two classes : A and B under packages com.acme :
A with Dubbo @Service
B with Spring @Service and Dubbo @Service
@ComponentScan scans this package first, and B will be a candidate of @Service Bean , and then @DubboComponentScan also scans same package , just A will be exported as Dubbo Remote interface , B will be missing.
The text was updated successfully, but these errors were encountered:
* Fixed#1116#1120#1121#1122#1141#1125
* DubboConfigConfiguration's Single and Multiple to be public classes
* @DubboComponentScan is compatible with Spring @service completely
* @service and @reference issues on <dubbo:annotation>
* To fix an issue on <dubbo:annotation> when id attribute is absent
* To change the prefixes of properties when @EnableDubboConfig binds
multiple Config Bean
rolandhe
pushed a commit
to rolandhe/dubbo
that referenced
this issue
Sep 9, 2019
* Fixedapache#1116apache#1120apache#1121apache#1122apache#1141apache#1125
* DubboConfigConfiguration's Single and Multiple to be public classes
* @DubboComponentScan is compatible with Spring @service completely
* @service and @reference issues on <dubbo:annotation>
* To fix an issue on <dubbo:annotation> when id attribute is absent
* To change the prefixes of properties when @EnableDubboConfig binds
multiple Config Bean
If Service bean annotated Dubbo
@Service
and Spring@Service
and@ComponentScan
executes earlier than@DubboComponentScan
, current been will not be a candidate of@Service
Bean.@DubboComponentScan
should consider this scenario:There are two classes :
A
andB
under packagescom.acme
:A with Dubbo
@Service
B with Spring
@Service
and Dubbo@Service
@ComponentScan
scans this package first, and B will be a candidate of@Service
Bean , and then@DubboComponentScan
also scans same package , just A will be exported as Dubbo Remote interface , B will be missing.The text was updated successfully, but these errors were encountered: