In Quarkus Extension, modelling resources are automatically deployed

camunda / camunda-bpm-platform

Flexible framework for workflow and decision automation with BPMN and DMN. Integration with Quarkus, Spring, Spring Boot, CDI.

https://camunda.com/

Apache License 2.0

4.08k stars 1.54k forks source link

In Quarkus Extension, modelling resources are automatically deployed #2617

Open ThorbenLindhauer opened 3 years ago

ThorbenLindhauer commented 3 years ago

This issue was imported from JIRA:

Field	Value
JIRA Link	CAM-13565
Reporter	@tasso94
Has restricted visibility comments	true

User Story (Required on creation):

To deploy a model to the engine, I can place a resource file (e.g., a BPMN file) into the resources folder of my application.

Technical Requirements (Required before implementation):

Resources or resource patterns can be defined via application.properties file
There is a predefined pattern to scan automatically for resources
Multiple deployments can be defined (e.g. through "named" deployment properties like quarkus.camunda.deployments."deployment-1".resources=...).

Links:

depends on https://jira.camunda.com/browse/CAM-13628
is related to https://jira.camunda.com/browse/SUPPORT-10186
is related to https://jira.camunda.com/browse/CAMPLAN-20

ThorbenLindhauer commented 2 years ago

This comment was imported from JIRA and written by user mg7jEVk

What is this name?

This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.

Will this also contain support for existing processes.xml files, allowing to create multiple process archives?

We would like to see this feature or a similar way of creating the same configuration.

The automated deployment of resources itself is a crucial feature for us, running an embedded engine with local model resources that are released as part of the software.

ThorbenLindhauer commented 2 years ago

This comment was imported from JIRA and written by user @tasso94

Hi mg7jEVk,

Thank you for this feedback!

We think support for a processes.xml based deployment mechanism isn't the way for Quarkus for various reasons.

What is your use case to create multiple process archives within a single Quarkus application?

Best, Tassilo

ThorbenLindhauer commented 2 years ago

This comment was imported from JIRA and written by user mg7jEVk

What is this name?

This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.

Hi Tassilo,

I agree that a specific XML file doesn't seem to fit the Quarkus approach. The reason we want to have separate process archives is that changes in one or a set of resources do not lead to redeployment and new versions of the resources in other archives. This prevents an unwieldy number of process definitions, particularly in engines where some processes or decisions change frequently and others do not. We typically group resources in classpath folders that match the archives for organisation.

Best, Tiese

ThorbenLindhauer commented 2 years ago

This comment was imported from JIRA and written by user @tasso94

Hi mg7jEVk,

Thank you for your feedback.

Best, Tassilo