GH-1014 Fix CustomRuntimeEventLoop to default to RoutingFunction
Resolves #1014
This commit is contained in:
@@ -1,3 +1,9 @@
|
||||
# Introduction
|
||||
|
||||
This example shows GraaalVM native spring-cloud-function application. The application itself is very simple and contains two functions - `uppercase` & `lowercase`.
|
||||
Unless specific value is specified as `handler`, the application will fall back on `RoutingFunction` where you can pass the routing instruction
|
||||
via `spring.cloud.function.definition` Message header. If using API Gateway you can pass such header as HTTP header.
|
||||
|
||||
# To run
|
||||
|
||||
## If you are on OSX Apple M1 Pro (arch64)
|
||||
@@ -11,7 +17,7 @@ $ docker build -t "al2-graalvm19:native-uppercase" .
|
||||
Start the container
|
||||
|
||||
```
|
||||
$ docker run -dit al2-graalvm19:native-uppercase
|
||||
$ docker run -dit -v `pwd`:`pwd` -w `pwd` -v ~/.m2:/root/.m2 al2-graalvm19:native-uppercase
|
||||
```
|
||||
|
||||
Now navigate to the image terminal. Your working directory is alredy set for the root of the project. You can verify it by executing `ls`.
|
||||
|
||||
Reference in New Issue
Block a user