Details
-
Feature Request
-
Resolution: Done
-
L3 - Default
-
None
Description
User Story (Required on creation):
As a user, I can extend Run's process engine with the help of plugins. Some (community) extensions make use of being registered via a process engine plugin, which cannot be used currently.
Functional Requirements (Required before implementation):
- I can add a JAR containing a process engine plugin to the userlib folder and activate it
- To be decided: Should the plugin be automatically registered (if yes, how is that technically meaningfully possible?) or should the plugin be configured in Run's configuration file (e.g. by referencing the class name)?
Technical Requirements (Required before implementation):
- Ideally this mechanism has no dependency on Spring for the user (e.g. having to annotate a plugin with Spring annotations is not great)
Alternative Solution
Currently, there is an alternative way to register process engine plugins by locating a custom class extending the ProcessEnginePlugin class marked as bean under the package namespace org.camunda.bpm.run. This leverages that Camunda Run is based on our Spring Boot Starter, which provides the aforementioned feature to register plugins, and Camunda Run does component scanning for this namespace.
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
1.
|
Provide a working example of building a process engine plugin with Camunda-Run |
|
Closed | Unassigned |