Observe Camel's Lifecycle events

[lburgazzoli]

No description provided.

[lburgazzoli]

There's some overlap between life-cycle and management events:

• LifecycleStrategy
• CamelEvent

@jamesnetherton @davsclaus wonder if we should limit life-cycle events to onComponent (add/remove) and onEndpoint (add/remove) and wrap them as custom CamelEvent

[lburgazzoli]

@jamesnetherton @davsclaus a possible implementation proposed as #1404

[davsclaus]

Okay so if we only listen for component add/remove endpoint add/remove is there a special reason for this? Just wonder

[lburgazzoli]

I was thinking about have just a single set of events, as example you can listen for Context start event with both a life-cycle callback and with a management event so there's some duplication and I didn't want to expose both to avoid confusion.

It relates to: https://issues.apache.org/jira/browse/CAMEL-11566

[lburgazzoli]

@davsclaus added the missing non overlapping events

[davsclaus]

Ah okay, so you wanted to present this to the camel-quarkus end users as a uniform api using standard java events. So you dont need to choose when to use lifecycle vs events.

Yeah ideally events should be for end users, and lifecycle for component developers where you need some special integration (spi interface).

But historically then there was only lifecycle in the start of Camel and events was added later, that was a bit tied to jmx events in the start.

However would likely be good to make end users go for events in camel-core over lifecycle.