jamesnetherton opened a new issue #2954: URL: https://github.com/apache/camel-quarkus/issues/2954
There's a potential bug in the gRPC extension where it's possible to define multiple consumers for the same service class. Meaning that the configuration of the last gRPC consumer defined defined in the `RouteBuilder` will 'win'. In reality, I'm not sure how common this use case would be. But in the plain Camel component it's possible to do this by using a different host or port combination on the consumer. In Camel Quarkus we have a fixed host / port driven by Quarkus gRPC, so it doesn't work. I've been thinking that we should divorce ourselves from `quarkus-grpc` and instead leverage `quarkus-grpc-common` to get the gRPC native support. Then we could have a closer UX to plain `camel-grpc` where all of the gRPC server configuration is dictated by the component / endpoint options. -- 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]
