AsperforMias opened a new issue, #3795: URL: https://github.com/apache/dubbo-go/issues/3795
### What problem would this solve? Since #3711, dubbo-go publishes interface-level ServiceDefinitions for Dubbo and non-IDL Triple services. dubbo-admin uses these documents for service search, service detail, the method list, and method detail. Triple services registered from a `.proto` (the `RegisterXxxHandler` path generated by `protoc-gen-go-triple`) are deliberately excluded. Reflecting the generated Go structs gives a lossy view of the proto: it misses the real field names, enums, oneofs, and well-known types. As a result, an IDL-based dubbo-go provider registers and serves traffic normally, but Admin does not list its services or methods. Most dubbo-go-samples providers use IDL, so this is the common case rather than an edge case. ### Proposed solution Build the definitions for IDL services from protobuf descriptors instead of reflection: - Message and enum types are named by their protobuf full name (`greet.GreetRequest`, `google.protobuf.Empty`). This is the name Triple IDL generic invocation uses. - Scalar and container fields use the same Java vocabulary as the existing builder (`java.lang.String`, `int`, `long`, `java.util.List<T>`, `java.util.Map<K,V>`). Admin resolves types by exact string, and its debug form only knows default values for that vocabulary. This also matches the shape Java Dubbo's `ProtobufTypeBuilder` produces. - Only unary methods are published. Admin generic invocation is unary-only, so a streaming method would advertise a call that cannot be made. Out of scope: a ZooKeeper definition publisher (separate PR) and an etcd publisher (later). -- 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]
