rajaluo commented on issue #15013:
URL: https://github.com/apache/dubbo/issues/15013#issuecomment-2560769024

   > ```
   > <dependency>
   >     <groupId>org.apache.dubbo.extensions</groupId>
   >     <artifactId>dubbo-remoting-http</artifactId>
   >     <version>3.3.1</version>
   > </dependency>
   > <dependency>
   >     <groupId>org.apache.dubbo.extensions</groupId>
   >     <artifactId>dubbo-rpc-http</artifactId>
   >     <version>3.3.1</version>
   > </dependency>
   > ```
   > 
   > And you can try the demo practice.
   > 
   > 
https://cn.dubbo.apache.org/zh-cn/blog/2023/10/07/%E5%BE%AE%E6%9C%8D%E5%8A%A1%E6%9C%80%E4%BD%B3%E5%AE%9E%E8%B7%B5%E9%9B%B6%E6%94%B9%E9%80%A0%E5%AE%9E%E7%8E%B0-spring-cloud-apache-dubbo-%E4%BA%92%E9%80%9A/
   
   
   @aofall It takes no effect too, is it because of the below codes(the full 
path of UserServiceFeign is  
org.apache.dubbo.samples.microservices.sc.rest.UserServiceFeign)?
   
   **@DubboReference(providedBy = "spring-cloud-provider-for-dubbo", check = 
false)**
       private UserServiceFeign userService;
   
   The error message below described that no provider available for service  
org.apache.dubbo.samples.microservices.sc.rest.UserServiceFeign:
   org.apache.dubbo.rpc.RpcException: No provider available from registry 
RegistryDirectory(registry: 127.0.0.1:8848)-Directory(invokers: 0[], 
validInvokers: 0[], invokersToReconnect: 0[]) **for service 
org.apache.dubbo.samples.microservices.sc.feign.UserServiceFeign** on consumer 
192.168.2.5 use dubbo version 3.3.2, please check status of providers(disabled, 
not registered or in blocklist).


-- 
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]

Reply via email to