Sorry to spam this mailing list. But I want to avoid any double
investigation:
We narrowed down the problem. Even if there is no error/warning the new
introduced check for circular-references in spring boot creates the problem.
The property below (default: false) enables the <2.6 behavior and our bean
is visible to the camel management and started
spring:
main:
allow-circular-references: true
Am Mo., 10. Jan. 2022 um 18:24 Uhr schrieb Michael Rambichler <
mich...@rambichler.at>:
> Short Update.
> We switched back to the previous used spring boot version.
> And it worked. Even that 2.4.1 is not supported with camel 3.14
>
> <spring.boot-version>2.4.1</spring.boot-version>
>
>
> Am Mo., 10. Jan. 2022 um 17:18 Uhr schrieb Michael Rambichler <
> mich...@rambichler.at>:
>
>> Hi all,
>>
>> we switched to Camel 3.14. and Spring Boot 2.16.2 and since that we face
>> following problem:
>>
>> We have a Custom EventNotifier. The bean is loaded in the SpringContext.
>> (checked)
>> But the automatic loading does not happen by camel engine. (it happens
>> previously with Camel 3.12)
>> The doStart() event from our EventNotifier never gets triggered.
>>
>> Was there any change in this area?
>>
>> If we call the managementStrategy.addEventNotifier() explicitly it works.
>> But this is only a workaround.
>>
>> @Override
>> public void configure() throws Exception {
>> super.configure();
>>
>> ManagementStrategy managementStrategy =
>> getContext().getManagementStrategy();
>> if (!managementStrategy.getEventNotifiers().contains(notifier)) {
>> log.info("Event notifier " + notifier + " is not already
>> registered.");
>> managementStrategy.addEventNotifier(notifier);
>> } else {
>> log.info("Event notifier " + notifier + " is already registered.");
>> }
>>
>>
