You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the "EventRegistry" is "disabled" (via a property or a java code)
Then it's possible to exclude from dependencies the "flowable-event-registry" JAR
The text was updated successfully, but these errors were encountered:
karel-cernohorsky
changed the title
Not possible to exclude the flowable-event-registry JAR even if EventRegistry disabled
Not possible to exclude the flowable-event-registry JAR even if EventRegistry disabled
Jun 10, 2024
karel-cernohorsky
changed the title
Not possible to exclude the flowable-event-registry JAR even if EventRegistry disabled
Not possible to exclude the flowable-event-registry JAR even if **EventRegistry** disabled
Jun 10, 2024
karel-cernohorsky
changed the title
Not possible to exclude the flowable-event-registry JAR even if **EventRegistry** disabled
Not possible to exclude the flowable-event-registry JAR even if EventRegistry disabled
Jun 10, 2024
Describe the bug
Even when disabling the EventRegistry via:
flowable.eventregistry.enabled = false
(see
@ConditionalOnEventRegistry
and its usage)and / or via:
it's still not possible to exclude from dependencies the following JAR:
flowable-event-registry
due to a missing check of whether the EventRegistry is disabled in:
flowable-engine/modules/flowable-engine/src/main/java/org/flowable/engine/impl/cfg/ProcessEngineConfigurationImpl.java
Line 1683 in 90b4b50
thus not bypassing the instantiation of:
flowable-engine/modules/flowable-engine/src/main/java/org/flowable/engine/impl/cfg/ProcessEngineConfigurationImpl.java
Line 1688 in 90b4b50
Expected behavior
Most likely via bypassing the instantiation of the
BpmnEventRegistryEventConsumer
in such a case.Code
Currently, we are forced to apply a dummy work-around, such as:
thus bypassing the instantiation of the
BpmnEventRegistryEventConsumer
in:flowable-engine/modules/flowable-engine/src/main/java/org/flowable/engine/impl/cfg/ProcessEngineConfigurationImpl.java
Lines 1683 to 1692 in 90b4b50
For comparison, the IDM engine's inclusion is properly checked in:
flowable-engine/modules/flowable-engine/src/main/java/org/flowable/engine/impl/cfg/ProcessEngineConfigurationImpl.java
Lines 1676 to 1681 in 90b4b50
Additional context
Flowable branches:
flowable-release-7.0.0
(tested v.7.0.1
)flowable-release-7.1.0
main
Spring Boot used in the version declared by the respective Flowable version.
relevant exclusions & dependencies in
build.gradle
:The text was updated successfully, but these errors were encountered: