[GitHub] [camel-quarkus] lburgazzoli commented on issue #9: quarkus-camel - Use MainSupport as base for running Camel

[GitBox <gi...@apache.org>]

lburgazzoli commented on issue #9: quarkus-camel - Use MainSupport as base for running Camel
URL: https://github.com/apache/camel-quarkus/issues/9#issuecomment-522317439
 
 
   As today `core` is responsible to act like a `main` but for better flexibility (i.e. for other to build on top of `core`) I think we need to split responsibilities like:
   
   1. `core` to set-up low level things such as:
       - camel context
       - registry
       - integration with quarkus event loop #131
   2. `main` to set up application related things, like:
       - initialize, start/stop the camel context created by `core`
       - discover routes
       - discover and register life-cycle interceptors (to allow i.e. camel-k to hook into the static init build processors)
       - integration with quarkus health checks #141 
       - integration with quarkus metrics #128
       - fire CDI events
   
   /cc @gnodet @davsclaus 
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services