Hi Kannan, Thank you for verifying my suspicion. In fact, what I have done was to manage the interceptors manually.
For each WAR: 1. extract all services 2. extract all interceptors 3. for each method, use io.grpc.InternalServerInterceptors.interceptCallHandlerCreate() to wrap the interceptors "manually" and create a BindableService which gets stored in a MutableHandlerRegistry. At the moment, the code is in a pull request: https://github.com/wildfly-extras/wildfly-grpc-feature-pack/pull/274. I expect there will be a release soon. -Ron On Friday, September 27, 2024 at 7:24:42 AM UTC-4 Kannan Jayaprakasam wrote: > Yes a single io.grpc.Server maintains a single registry as you pointed > out. You could create one io.grpc.Server instance for each WAR listening > on distinct ports. > > On Monday, September 16, 2024 at 10:46:20 PM UTC+5:30 Ronald Sigal wrote: > >> Hi, >> >> My goal is to have a single gRPC port such that services / interceptors >> in each Web Archive are segregated from other WARs. >> >> It seems that a io.grpc.internal.ServerImpl monitoring a port has a >> single >> HandlerRegistry for methods and a single field for holding all >> ServerInterceptors. >> >> Would I have to set up a port for each WAR to keep things separate? >> >> By the way, the point of the project is to incorporate gRPC into the >> WildFly application >> server. >> >> Thanks, >> Ron Sigal >> > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/8023cf68-cefe-493e-9544-abfc130c33f6n%40googlegroups.com.
