Hello.
Do you mean that in our case all these projects that are built and
deployed as a single bundle with multiple blueprints and Camel
contexts MUST be "exploded" in many bundles and as many configurations
file with replicated values ?
Thanks.
Regards
Le mar. 29 nov. 2022 à 09:44, Claus Ibsen
Hi
An app is classloader isolated, eg a WAR in Apache Tomcat, an OSGi bundle,
a Spring Boot app, etc.
On Tue, Nov 29, 2022 at 9:18 AM Ephemeris Lappis
wrote:
> Hello.
>
> We're looking for the constraints that may exist to migrate our
> projects from Camel 2.x to 3.x.
>
> One of them is mention
Hello.
We're looking for the constraints that may exist to migrate our
projects from Camel 2.x to 3.x.
One of them is mentioned in
https://camel.apache.org/manual/camel-3-migration-guide.html, about
multiple Camel contexts in the same application.
I'd like to be sure about what is an "applicatio
e}}
http://{{smx.hostname}}/routes/${header.sysXXX}/${header.localRoutes}/${header.actionsRoutes}
http://dummyhost"; />
1000
...
... Another routes
Hope it's help
-Message d'origine-
De : Martin Lichtin
Envoyé : 27 août 2021 10:37
À : users@camel.apache.org
Objet
eader.localRoutes}/${header.actionsRoutes}
http://dummyhost"; />
1000
...
... Another routes
Hope it's help
-Message d'origine-
De : Martin Lichtin
Envoyé : 27 août 2021 10:37
À : users@camel.apache.org
Objet : Migration from 2.x to 3.x
Hi,
the mig
Hi,
the migration says
"Support for multiple CamelContexts has been removed and only 1 CamelContext per
deployment is supported."
The term "deployment" seem loose.
My concern here is that in OSGi each bundle has its own CamelContext (e.g. via
blueprint configuration), how will that work?
- M
