ppalaga commented on issue #4657: URL: https://github.com/apache/camel-quarkus/issues/4657#issuecomment-1478581376
> Does this mean that the communication between different camel contexts will no longer be supported? Camel Quarkus always supported only a single CamelContext per application. Moreover, its life cycle of the CamelContext is controlled by Camel Quarkus rather than by the application developer. The mindset behind Camel Quarkus is mostly motivated by microservices: there is always only one deployment/application per JVM. There is no traditional application server (like WildFly) that would be able to host multiple apps. Quarkus framework takes care for providing some minimal embedded app-server-like environment to expose your app on the network. So if you really need multiple CamelContexts on Camel Quarkus, you probably need multiple applications communicating through the network. -- 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. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
