Re: replacement for direct-vm component

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 w

Re: replacement for direct-vm component

>From the migration guide from Camel 2 to 3: Multiple CamelContexts per application not supported Support for multiple CamelContexts has been removed and only 1 CamelContext per dep

Re: replacement for direct-vm component

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 cal

Re: replacement for direct-vm component

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"

replacement for direct-vm component

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/C