You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -44,7 +44,7 @@ The starter supports also the `in-process server`, which should be used for tes
44
44
inProcessServerName: myTestServer <2>
45
45
----
46
46
<1> Disables the default server (`NettyServer`).
47
-
<2> Enables the in-process server.
47
+
<2> Enables the `in-process` server.
48
48
49
49
[NOTE]
50
50
If you enable both the `NettyServer` and `in-process` server, they will both share the same instance of `HealthStatusManager` and `GRpcServerBuilderConfigurer` (see <<Custom gRPC Server Configuration>>).
@@ -154,8 +154,6 @@ public class GreeterService extends GreeterGrpc.GreeterImplBase{
154
154
----
155
155
156
156
157
-
158
-
159
157
=== Custom gRPC Server Configuration
160
158
161
159
To intercept the `io.grpc.ServerBuilder` instance used to build the `io.grpc.Server`, you can add bean that inherits from `org.lognet.springboot.grpc.GRpcServerBuilderConfigurer` to your context and override the `configure` method. +
@@ -180,8 +178,9 @@ public class MyGRpcServerBuilderConfigurer extends GRpcServerBuilderConfigurer()
180
178
----
181
179
182
180
[NOTE]
183
-
If you enable both `NettyServer` and `in-process` servers, the `configure` method will be invoked on the same instance og configurer.
184
-
If you need to differentiate between the passed `serverBuilder`s, you can check the type. This is the current limitation.
181
+
If you enable both `NettyServer` and `in-process` servers, the `configure` method will be invoked on the same instance of configurer. +
182
+
If you need to differentiate between the passed `serverBuilder`s, you can check the type. +
0 commit comments