Describe the bug

When using the same .proto file for both a class implementing the Mutiny API and another class using the default gRPC API in Quarkus, only the service implemented with the default API appears in the gRPC services list.

The service using the Mutiny API gets removed and is not available. However, if I create a separate .proto file and use it for one of the implementations, both services show up in the Dev UI under gRPC services.

Expected behavior

I expected both services to be available for connection and visible in the Dev UI under gRPC services. It should not matter if they are using the same .proto file.

Actual behavior

Using the grpc-plain-text-quickstart, I created a class using the default api example from the documentation. When testing both the default API and mutiny API, I realized that one endpoint was missing. The default API displays in the gRPC · Services, however the mutiny api got removed. I found it in the ARC - removed components (dev-ui) and they are also not available when I call it.

How to Reproduce?

Get the grpc-plain-test-quickstart
Add a class to io.quarkus.grpc.examples.hello;
use the extends GreeterImplBase

insert the code
@OverRide
public void sayHello(HelloRequest request, StreamObserver responseObserver) {
String name = request.getName();
HelloReply reply = HelloReply.newBuilder().setMessage("Hello " +
name).build();
responseObserver.onNext(reply);
responseObserver.onCompleted();
}

compile and run quarkus:dev

Output of uname -a or ver

Linux L91PLPG3 5.10.16.3-microsoft-standard-WSL2 #1 SMP Fri Apr 2 22:23:49 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Output of java -version

openjdk version "22.0.1" 2024-04-16

Quarkus version or git rev

3.16.1

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)

Additional information

No response