Skip to content

Latest commit

 

History

History

quarkus-extension

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

Camunda Platform Quarkus Extensions

Maven Central camunda manual latest

This sub-project provides Camunda Platform Quarkus Extensions that allow you to add behavior to your Quarkus application by adding dependencies to the classpath.

You can find the documentation on the Camunda Platform Quarkus Extensions here.

We also provide some useful examples at our camunda-bpm-examples repository.

<dependency>
  <dependency>
    <groupId>org.camunda.bpm.quarkus</groupId>
    <artifactId>camunda-bpm-quarkus-engine</artifactId>
    <version>${version.camunda}</version><!-- place Camunda version here -->
  </dependency>
</dependency>

To configure a Camunda Platform Quarkus extension, you can use an application.properties file. It can look like the following:

# process engine configuration
quarkus.camunda.cmmn-enabled=false
quarkus.camunda.dmn-enabled=false
quarkus.camunda.history=none
quarkus.camunda.initialize-telemetry=false

# job executor configuration
quarkus.camunda.job-executor.thread-pool.max-pool-size=12
quarkus.camunda.job-executor.thread-pool.queue-size=5
quarkus.camunda.job-executor.max-jobs-per-acquisition=5
quarkus.camunda.job-executor.lock-time-in-millis=500000
quarkus.camunda.job-executor.wait-time-in-millis=7000
quarkus.camunda.job-executor.max-wait=65000
quarkus.camunda.job-executor.backoff-time-in-millis=5

# custom data source configuration and selection
quarkus.datasource.my-datasource.db-kind=h2
quarkus.datasource.my-datasource.username=camunda
quarkus.datasource.my-datasource.password=camunda
quarkus.datasource.my-datasource.jdbc.url=jdbc:h2:mem:camunda;TRACE_LEVEL_FILE=0;DB_CLOSE_ON_EXIT=FALSE
quarkus.camunda.datasource=my-datasource

Local Build

Executing the Tests

mvn clean install -Pquarkus-tests


Quarkus and JUEL bytecode incompatibilities

Context: JUEL was built with a different Java version. Quarkus won't pick up new build changes. For more information, check #3419 (comment)

Solution: If you notice juel exceptions like below, delete /juel/target folder and run the Quarkus build again.

Stacktrace
Caused by: java.lang.VerifyError: Bad type on operand stack
Exception Details:
Location:
org/camunda/bpm/engine/impl/el/JuelExpressionManager.<init>(Ljava/util/Map;)V @28: putfield
Reason:
Type 'org/camunda/bpm/impl/juel/ExpressionFactoryImpl' (current frame, stack[1]) is not assignable to 'org/camunda/bpm/impl/juel/jakarta/el/ExpressionFactory'
Current Frame:
bci: @28
flags: { }
locals: { 'org/camunda/bpm/engine/impl/el/JuelExpressionManager', 'java/util/Map' }
stack: { 'org/camunda/bpm/engine/impl/el/JuelExpressionManager', 'org/camunda/bpm/impl/juel/ExpressionFactoryImpl' }
Bytecode:
0000000: 2ab7 0007 2abb 000c 59b7 000e b500 0f2a
0000010: 03b5 0013 2abb 0017 59b7 0019 b500 1a2a
0000020: 2bb5 001e b1```
</details>