A quickstart project that processes travellers in the system. It's main purpose is to illustrate local service invocation.
This example shows
-
invoking local service class that is a injectable bean
-
control flow based on service calls
-
New Travelers Diagram
- New Travelers Diagram Properties
- New Travelers Diagram Properties
- Store Traveler Service Call
- Store Traveler Service Call
- Store Traveler Service Call
- Stored Traveler Gateway Yes Connector
- Stored Traveler Gateway No Connector
- Greet New Traveler Service Call
- Greet New Traveler Service Call
- Audit Traveler Service Call
- Audit Traveler Service Call
- Multi Params Process
- Multi Params Diagram Properties
- Multi Params Diagram Properties
- Hello Service Calls
- Hello Service Calls
You will need:
- Java 17+ installed
- Environment variable JAVA_HOME set accordingly
- Maven 3.9.6+ installed
When using native image compilation, you will also need:
- GraalVM 19.1+ installed
- Environment variable GRAALVM_HOME set accordingly
- Note that GraalVM native image compilation typically requires other packages (glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM installation documentation for more details.
mvn clean compile quarkus:dev
NOTE: With dev mode of Quarkus you can take advantage of hot reload for business assets like processes, rules, decision tables and java code. No need to redeploy or restart your running application.
mvn clean package
java -jar target/quarkus-app/quarkus-run.jar
or on windows
mvn clean package
java -jar target\quarkus-app\quarkus-run.jar
Note that the following configuration property needs to be added to application.properties
in order to enable automatic registration of META-INF/services
entries required by the workflow engine:
quarkus.native.auto-service-loader-registration=true
Note that this requires GRAALVM_HOME to point to a valid GraalVM installation
mvn clean package -Pnative
To run the generated native executable, generated in target/
, execute
./target/process-service-calls-quarkus-runner
You can take a look at the OpenAPI definition - automatically generated and included in this service - to determine all available operations exposed by this service. For easy readability you can visualize the OpenAPI definition file using a UI tool like for example available Swagger UI.
In addition, various clients to interact with this service can be easily generated using this OpenAPI definition.
When running in either Quarkus Development or Native mode, we also leverage the Quarkus OpenAPI extension that exposes Swagger UI that you can use to look at available REST endpoints and send test requests.
To make use of this application it is as simple as putting a sending request to http://localhost:8080/travellers
with following content
{
"traveller" : {
"firstName" : "John",
"lastName" : "Doe",
"email" : "[email protected]",
"nationality" : "American",
"address" : {
"street" : "main street",
"city" : "Boston",
"zipCode" : "10005",
"country" : "US" }
}
}
Complete curl command can be found below:
curl -X POST -H 'Content-Type:application/json' -H 'Accept:application/json' -d '{"traveller" : { "firstName" : "John", "lastName" : "Doe", "email" : "[email protected]", "nationality" : "American","address" : { "street" : "main street", "city" : "Boston", "zipCode" : "10005", "country" : "US" }}}' http://localhost:8080/travellers
After the above command you should see a log similar to the following
To call Hello Service send a request to http://localhost:8080/multiparams
with following content
{
"name" : "John",
"age" : 44,
}
Complete curl command can be found below:
curl -X POST -H 'Content-Type:application/json' -H 'Accept:application/json' -d '{"name" : "John", "age" : 44}' http://localhost:8080/multiparams
After the above command you should see a log similar to the following