-
Notifications
You must be signed in to change notification settings - Fork 26.4k
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
[Bug] dubbo-samples-spring-boot-idl #14781
Comments
I'm going to try to fix it. |
Your dubbo version is 3.3.0-beta.2, not 3.3.0 |
Sorry for the clerical error. I have corrected that I did encounter this problem with 3.0-beta2. However, I also tested 3.3.0 and encountered the same problem. |
I tested 3.3.0 and it work fine. |
Are you also unable to start it in IDEA? Currently, I haven't encountered any issues using version 3.3.0 in IDEA.@11D-Beyonder |
I did not find the cause of the problem, but there are some clues to offer. I came to the conclusion that the values of For example, if the IDL file is like this: package org.apache.dubbo.springboot.demo.idl;
option java_package = "org.apache.dubbo.springboot.demo.idl"; or the However, if the package org.apache.dubbo.springboot.demo.idl;
option java_package = "org.apache.dubbo.springboot.demo.api"; The request to both I'm a beginner to Dubbo, and I don't know if this is a Bug or a design consideration. Hope to get some answers, thank you. @heliang666s |
This is not a bug; it is intentionally designed this way. Since proto files are used, the In simple terms, you need to ensure that the import paths in both the provider and consumer match the |
Pre-check
Search before asking
Apache Dubbo Component
Java Samples (apache/dubbo-samples)
Dubbo Version
Dubbo Java: 3.3.0-beta2
Java: 17
I follow the step in dubbo-samples-spring-boot-idl/README.md.
When start provider,
curl
fail.The log in provider is
Steps to reproduce this issue
follow the step in README.md.
What you expected to happen
I don't know
Anything else
No response
Are you willing to submit a pull request to fix on your own?
Code of Conduct
The text was updated successfully, but these errors were encountered: