davsclaus commented on issue #1399: URL: https://github.com/apache/camel-quarkus/issues/1399#issuecomment-647466338
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. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
