Quarkus extension uses right class loader in DEVELOPMENT and TEST launch modes

[tasso94]

User Story (Required on creation)

As a user, I can run tests and work in the development mode with my java delegates correctly picked up.

Context

• In launch modes DEVELOPMENT and TEST, Quarkus uses the wrong class loader when executing processes synchronously and asynchronously.
  • Two class loaders, the Base Runtime and Runtime, are available to allow the hot reloading of resources ¹.
• We currently have two workarounds for the Job Executor context switch ² and the default class loader ³ set in the process engine configuration. In both situations, the Quarkus Base Runtime instead of the Runtime class loader is used.

Functional Requirements (Required before implementation)

Quarkus extension uses the right class loader in DEVELOPMENT and TEST launch modes.

Technical Requirements (Required before implementation)

Limitations of Scope

Hints

Links

• https://jira.camunda.com/browse/SUPPORT-19133
• https://jira.camunda.com/browse/SUPPORT-17679
• https://jira.camunda.com/browse/SUPPORT-20108

Breakdown

Pull Requests

Beta Give feedback

No tasks being tracked yet.

Dev2QA handover

• Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

Footnotes

1. https://quarkus.io/guides/class-loading-reference#classloader-implementations ↩

2. https://jira.camunda.com/browse/SUPPORT-19133?focusedCommentId=314653&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-314653 ↩

3. https://jira.camunda.com/browse/SUPPORT-17679?focusedCommentId=295262&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-295262 ↩