[GitHub] [camel-quarkus] lburgazzoli edited a comment on issue #1037: Support Quarkus command mode
lburgazzoli edited a comment on issue #1037: URL: https://github.com/apache/camel-quarkus/issues/1037#issuecomment-617833921 We don't need to control the bootstrap by an option but instead each "boostrap extension" should override the default `assembler` so `quarkus.camel.main.enabled` should can go away 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
[GitHub] [camel-quarkus] lburgazzoli edited a comment on issue #1037: Support Quarkus command mode
lburgazzoli edited a comment on issue #1037: URL: https://github.com/apache/camel-quarkus/issues/1037#issuecomment-617614160 I also think we can revisit the way we do bootstrap camel-quarkus (naming is purely indicative): - embedded (core) - routes are added to the camel context directly - context need to be programmatically configured - main - routes and configuration classes are managed by camel-main - support for command line - support for configuration through properties - static (aka lightweight) - routes are added to the camel context directly - some limitation may happen - context need to be programmatically configured We can then provide `main` and `static` behaviour through extensions so depending of the end user need we may achieve different optimization or behaviours without cluttering the code too much. /cc @gnodet @davsclaus WDYT ? 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
[GitHub] [camel-quarkus] lburgazzoli edited a comment on issue #1037: Support Quarkus command mode
lburgazzoli edited a comment on issue #1037: URL: https://github.com/apache/camel-quarkus/issues/1037#issuecomment-617614160 I also think we can revisit the way we do bootstrap camel-quarkus (naming is purely indicative): - embedded - routes are added to the camel context directly - context need to be programmatically configured - main - routes and configuration classes are managed by camel-main - support for command line - support for configuration through properties - static (aka lightweight) - routes are added to the camel context directly - some limitation may happen - context need to be programmatically configured We can then provide `main` and `static` behaviour through extensions so depending of the end user need we may achieve different optimization or behaviours without cluttering the code too much. /cc @gnodet @davsclaus WDYT ? 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
