Quarkus Integration

The ASEE Flow Engine can be used in a Quarkus application by using the provided Quarkus Extension. Quarkus Extensions add behavior to your Quarkus application by adding dependencies to the classpath. The ASEE Flow Engine Quarkus Extension will pre-configure the ASEE Flow process engine, so it can be easily used in a Quarkus application. If you are not familiar with Quarkus, have a look at the getting started guide. To enable ASEE Flow Engine autoconfiguration, add the following dependency to your pom.xml:

<dependency>
  <groupId>org.aseeflow.bpm.quarkus</groupId>
  <artifactId>aseeflow-bpm-quarkus-engine</artifactId>
  <version>1.0.0</version>
</dependency>

This will add the ASEE Flow engine v.7.23.0 to your dependencies.

Supported deployment scenarios

ASEE Flow supports the following deployment scenario:

executable JAR with one embedded process engine.

There are other possible variations that might also work, but are not tested by ASEE Flow at the moment.

In this section

Quarkus Version Compatibility — Supported Quarkus versions.
Engine CDI Integration — Use the engine with Quarkus CDI.
Quarkus Extension Configuration — Configure the Quarkus extension.
Resource Deployments — Deploy process resources.

​Supported deployment scenarios

​In this section

Supported deployment scenarios

In this section