Spring/spring-grpc
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typo in docs

Browse Source 
Signed-off-by: mackey0225 <masaki.asano0225@gmail.com>
This commit is contained in:
mackey0225
2025-03-16 12:02:25 +09:00
committed by Dave Syer
parent c0b8b630eb
commit cfb14ba7e0
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
spring-grpc-docs/README.md
View File

@@ -2,7 +2,7 @@
## README
The top level README and CONTRIBUTING guidleines documentation are generated from sources in this module on `mvn package` using [`asciidoctor-reducer`](https://github.com/asciidoctor/asciidoctor-reducer) and [`downdoc`](https://github.com/opendevise/downdoc).
The top level README and CONTRIBUTING guidelines documentation are generated from sources in this module on `mvn package` using [`asciidoctor-reducer`](https://github.com/asciidoctor/asciidoctor-reducer) and [`downdoc`](https://github.com/opendevise/downdoc).
## Configuration Properties
The Spring gRPC configuration properties are automatically documented as follows:

4
spring-grpc-docs/src/main/antora/modules/ROOT/pages/client.adoc
View File

@@ -94,7 +94,7 @@ The prefix `secure` is used as a bean definition name prefix, so the resulting b
This feature is useful when you want to have multiple instances of the same stub class with different configurations.
N.B. The `ClientRegistrationRepository` in the example is injected via an `ObjectProvider` which is not called directly to avoid early instantiation.
The customizer has to run very early in the application lifecycle, so you always want to follow this pattern if you need to inject depdendencies to build the channel options.
The customizer has to run very early in the application lifecycle, so you always want to follow this pattern if you need to inject dependencies to build the channel options.
== Create a Client Manually
@@ -310,7 +310,7 @@ The rest is the configuration of the SSL bundle itself, in this case using JKS e
=== HTTP Headers
Spring gRPC provides a couple of interceptor that can be used to provide security to your gRPC clients.
There is one for Basic HHTP authentication and one for OAuth2 (bearer tokens).
There is one for Basic HTTP authentication and one for OAuth2 (bearer tokens).
Here's an example of creating a channel that uses Basic HTTP authentication:
[source,java]

2
spring-grpc-docs/src/main/antora/modules/ROOT/pages/server.adoc
View File

@@ -8,7 +8,7 @@ The `Server` is the gRPC server that listens for incoming requests and routes th
== Create a gRPC Service
To create a gRPC server, you need to provide one or more beans of type `BindableService`.
There are some `BindableServices` available off the shelf that you could include in your application (an example is the reflection service from the `grpc-services` artifact which allows clients to browse the metadata of your services and download the Portobuf files).
There are some `BindableServices` available off the shelf that you could include in your application (an example is the reflection service from the `grpc-services` artifact which allows clients to browse the metadata of your services and download the Protobuf files).
Very commonly, you will create your own `BindableService` by extending the generated service implementation from your Protobuf file.
The easiest way to activate it is to simply add a Spring `@Service` annotation to the implementation class and have it picked up by the `@ComponentScan` in your Spring Boot application.