User Story (Required on creation):
I was trying to extend the processing of history events and ran into the following problems:
- I can`t replaced/remove HistoryParseListener in camunda configuration via plugin. This is necessary so that I can use my BpmnParseListener implementation(like as HistoryParseListener).
- It is difficult to extend the HistoryEvent when writing custom history handlers(for example, I tried to add a business key to the HistoryEvent (not persist it in the database, but just pass it to the handler)
Functional Requirements (Required before implementation):
- Add the ability to disable default BPMN parse listeners
- Add the ability to extend the HistoryEvent via composition
Technical Requirements (Required before implementation):
- In class ProcessEngineConfigurationImpl add property as boolean to disable HistoryParseListener in ProcessEngineConfigurationImp #getDefaultBPMNParseListeners
- In HistoryEventHandler add new methods with one parameter with type B. B is interface with getter for HistoryEvent. Such a scheme will allow to expand the context of the history handler by replacing the implementation of B.
Limitations of Scope (Optional):
Hints (optional):
Feature Request
L3 - Default