-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
7.17.0
-
None
User Story (Required on creation):
Hi,
The following issue is about a code part in the Camunda Spring Boot Starter.
We are using custom ApplicationEvent in our application to control certain lifecycle aspects during the startup. This means also that we have some subsequent migrations regarding Camunda. This migration is executed after a certain event has been published. Unfortunately, Camunda already starts on the ApplicationReadyEvent (as can be seen in the ProcessApplicationEventPublisher), which is too early for us. In order to give developers more control, it would be sufficient if one could at least overwrite the beans in the CamundaBpmAutoConfiguration without using something like the spring.main.allow-bean-definition-overriding-Setting.
It would thus be very useful if the beans in the CamundaBpmAutoConfiguration would be marked with ConditionalOnMissingBean. This would allow easy and clean "overring" of the beans in question with custom logic.
Functional Requirements (Required before implementation):
Technical Requirements (Required before implementation):
Limitations of Scope (Optional):
Hints (optional):
This is the controller panel for Smart Panels app
[CAM-14784] Allow overwriting beans in CamundaBpmAutoConfiguration
| Assignee | New: Nikola Koevski [ nikola.koevski ] |
| Description |
Original:
h3. User Story (Required on creation):
Hi, We are using custom _ApplicationEvent_ in our application to control certain lifecycle aspects during the startup. This means also that we have some subsequent migrations regarding Camunda. This migration is executed after a certain event has been published. Unfortunately, Camunda already starts on the _ApplicationReadyEvent_ (as can be seen in the {_}ProcessApplicationEventPublisher{_}), which is too early for us. In order to give developers more control, it would be sufficient if one could at least overwrite the beans in the _CamundaBpmAutoConfiguration_ without using something like the {_}spring.main.allow-bean-definition-overriding{_}-Setting. It would thus be very useful if the beans in the _CamundaBpmAutoConfiguration_ would be marked with {_}ConditionalOnMissingBean{_}. This would allow easy and clean "overring" of the beans in question with custom logic. h3. Functional Requirements (Required before implementation): h3. Technical Requirements (Required before implementation): h3. Limitations of Scope (Optional): h3. Hints (optional): |
New:
h3. User Story (Required on creation):
Hi, The following issue is about a code part in the Camunda Spring Boot Starter. We are using custom _ApplicationEvent_ in our application to control certain lifecycle aspects during the startup. This means also that we have some subsequent migrations regarding Camunda. This migration is executed after a certain event has been published. Unfortunately, Camunda already starts on the _ApplicationReadyEvent_ (as can be seen in the {_}ProcessApplicationEventPublisher{_}), which is too early for us. In order to give developers more control, it would be sufficient if one could at least overwrite the beans in the _CamundaBpmAutoConfiguration_ without using something like the {_}spring.main.allow-bean-definition-overriding{_}-Setting. It would thus be very useful if the beans in the _CamundaBpmAutoConfiguration_ would be marked with {_}ConditionalOnMissingBean{_}. This would allow easy and clean "overring" of the beans in question with custom logic. h3. Functional Requirements (Required before implementation): h3. Technical Requirements (Required before implementation): h3. Limitations of Scope (Optional): h3. Hints (optional): |
| Status | Original: Open [ 1 ] | New: Ready [ 10005 ] |
| Assignee | Original: Nikola Koevski [ nikola.koevski ] | New: Tobias Metzke-Bernstein [ tobias.metzke ] |
| Assignee | Original: Tobias Metzke-Bernstein [ tobias.metzke ] |