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
We are pleased to announce some work we've been doing to integrate gRPC
into Red Hat's WildFly application server (https://www.wildfly.org/). There
are two projects:
1. WildFly has a new grpc subsystem
(https://www.wildfly.org/news/2023/06/12/grpc-subsystem/) which will detect
and expose gRPC
24 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 Ro
Release 1.0.0.Alpha6 of the *resteasy-grpc* project(a bridge between gRPC
and Jakarta REST) is now available. It adds lists and sets to the supported
semantics of Jakarta REST projects.
** grpc-bridge *
(https://central.sonatype.com/artifact/dev.resteasy.grpc/grpc-bridge/1.0.0.Alpha6):
Sca