-
Notifications
You must be signed in to change notification settings - Fork 917
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
GO and JAVA cannot communicate with each other due to case issues #2569
Comments
PascalCase should be used, in java side PascalCase and camelCase always generate camelCase method name , but in go side currently method name is update: go 3.1.x is always PascalCase,3.2 will be PascalCase also #2570 |
If you use PascalCase, an error will occur when java calls java or go services through the triple protocol. java server return: |
please create a demo project to reproduce, java client call java server is a basic usage,I'm confused how it happen |
see this example Is spring proxy problem, the |
I still can't reproduce you problem, but if you think the |
Environment
Issue description
Should the rpc method in the proto file be defined as PascalCase or camelCase?
No matter which one, go and java are currently unable to communicate with each other.
rpc method using
PascalCase
:result: java client convert method name to camelCase
UNIMPLEMENTED : Method : greet not found of service:com.example.triple.service.GreeterService
, maybe because java server return status isUNIMPLEMENTED(12)
cannot find method [greet] of service [com.example.GreeterService] in dubbo
rpc method using
camelCase
(not followed protobuf style guid):result: go server convert method name to PascalCase, but serviceInfo still camelCase
unknown method Greet for service com.example.GreeterService
unknown method Greet for service com.example.GreeterService
The text was updated successfully, but these errors were encountered: