fixing whcih typo
This commit is contained in:
@@ -49,7 +49,7 @@ payload via `data` operation. Then we use one of the `retrieve` operations that
|
||||
|
||||
As you can see from the preceding examples, we provide function definition as a value to `route(..)` operator of `RSocketRequester.Builder`.
|
||||
However that is not the only way. You can also use standard `spring.cloud.function.definition` property as well as `spring.cloud.function.routing-expression` or property or `MessageRoutingCallback` on the server side of the RSocket interaction (see "Function Routing and Filtering" section of reference manual).
|
||||
This raises a question of _order_ and _priorities_ when it comes to reconsiling a conflict in the event several ways of providing definition are used. So it is a mater of clearly stating the rule whcih is:
|
||||
This raises a question of _order_ and _priorities_ when it comes to reconsiling a conflict in the event several ways of providing definition are used. So it is a mater of clearly stating the rule which is:
|
||||
|
||||
***1 - MessageRoutingCallback***
|
||||
The `MessageRoutingCallback` takes precedence over all other ways of providing function definition resolution.
|
||||
@@ -96,4 +96,4 @@ So you can see `--spring.cloud.function.definition=reverse>localhost:" + portA +
|
||||
|
||||
### Samples
|
||||
|
||||
You can also look at one of the [RSocket samples](https://github.com/spring-cloud/spring-cloud-function/tree/master/spring-cloud-function-samples/function-sample-cloudevent-rsocket) that is also introduces you to Cloud Events
|
||||
You can also look at one of the [RSocket samples](https://github.com/spring-cloud/spring-cloud-function/tree/master/spring-cloud-function-samples/function-sample-cloudevent-rsocket) that is also introduces you to Cloud Events
|
||||
|
||||
Reference in New Issue
Block a user