Actually, if I read that correctly, it just means that applications using more than one camel context are likely to break - there's nothing preventing an application from actually trying to do so.
Anyway, I know what I must do now for this migration. Thanks. Art On 2023/11/07 19:11:27 ski n wrote: > From the migration guide from Camel 2 to 3: > > <https://camel.apache.org/manual/camel-3-migration-guide.html#_multiple_camelcontexts_per_application_not_supported>Multiple > CamelContexts per application not supported > > Support for multiple CamelContexts has been removed and only 1 CamelContext > per deployment is supported. The latter was not recommended anyway and was > also not 100% implemented (for example in camel-cdi). For Camel 3 only 1 > CamelContext per deployment is recommended and supported. > > The context attribute on the various Camel annotations such as > @EndpointInject, @Produce, @Consume etc. has therefore been removed. > > Source: https://camel.apache.org/manual/camel-3-migration-guide.html > > So this basically means that all your routes runs in one CamelContext (per > JVM). Don't know what happens when you run multiple “applications” in one > JVM, but in Camel 3.21 + or Camel 4 the route in those applications cannot > interact with each other directly. > > Raymond > > > > > > > On Tue, Nov 7, 2023 at 7:58 PM Arthur Naseef <artnas...@apache.org> wrote: > > > Can you explain "there is only one CamelContext"? How is that > > ensured/enforced? > > > > Art > > > > On 2023/11/07 18:33:02 ski n wrote: > > > I think the direct-vm was created in Camel 2 when you could have multiple > > > CamelContexts (for example in Karaf). When you would run multiple > > > CamelContexts and you want call another route then you needed direct-vm. > > > Since Camel 3 there is only one CamelContext, thus in most cases you can > > > use "direct" (synchronous invocation) or "seda" (asynchronous > > invocation). > > > > > > If you have multiple contexts now (assuming these are running in separate > > > JVM's) then you require something like ActiveMQ or RabbitMQ as an > > > intermediary broker. > > > > > > Raymond > > > > > > On Tue, Nov 7, 2023 at 6:37 PM Arthur Naseef <artnas...@apache.org> > > wrote: > > > > > > > As posted on the ASF slack camel channel: > > > > > > > > Hey guys - what is the camel 4 replacement for direct-vm? Looking > > around, > > > > I just see "deprecated" and no indication what alternative is expected > > to > > > > be used. > > > > > > > > Even comments in the related Jira ticket are quiet on it: > > > > https://issues.apache.org/jira/browse/CAMEL-19132 (edited) > > > > > > > > @davsclaus > > > > looks like you worked on this :point_up: > > > > > > > > > > > > Art > > > > > > > > > >
