Hi,

Regarding camel-cdi, it has been deprecated in 2.x and removed in 3.x AFAIK now 
you are supposed to use camel-blueprint instead.
Regarding camel-mongodb, it has been removed in 3.16.0 because we met some 
problems when upgrading the version of the driver, if really needed please 
create a Jira ticket in the Camel project, I will try to find a solution to put 
it back.

Regards,
Nicolas



________________________________
From: Bert Speckels <bert.speck...@gmail.com>
Sent: Monday, September 5, 2022 12:44
To: users@camel.apache.org <users@camel.apache.org>
Subject: Re: Camel and OSGI support

Hi Again

In fact, I'm extremely frustrated now. So excuse me if I sound a little
rude at this point. Actually I'm not like that. But not much remains of the
promising approach with Camel and Apache Karaf... similar to our first
approach with Quarkus.

So far I've only encountered obstacles trying to use the following in
Karaf.

CDI (most important)
camel-cdi apparently no longer exists as an OSGI bundle and pax-cdi alone
is not enough, because CDI (injection) is mainly used when building routes.
As far as I understand, this is only possible with Camel-CDI.

MongoDB
Camel-mongo doesn't seem to exist either. It may be sufficient here to
address the MongoDB driver directly, since we probably do not necessarily
need the Camel-specific MongoDB API. The only thing missing is a suitable
OR mapper with OSGI support.

EndpointDSL
camel-endpointsdsl does not support OSGI. However, there is an alternative
to this, although I don't really like concatenating configuration
parameters in a string.

It's extremely frustrating right now having to figure all of this out
yourself. I just hope that one of you can explain to me that CDI still
works with Camel and Karaf.

WIth kind regards
Bert.

Am So., 4. Sept. 2022 um 15:42 Uhr schrieb Bert Speckels <
bert.speck...@gmail.com>:

> Hello there
>
> I'm a bit desperate at the moment: We're switching our Camel routes (in a
> monolith, Camel 3.14.2) to OSGI bundles (Apache Karaf and upgrade to Camel
> 3.18.1). Unfortunately I have some difficulties with this.
>
> For one thing, I'm missing a few Camel features: Unfortunately,
> "camel-endpointsdsl" doesn't exist as an OSGI feature/bundle, right?
> Neither 3.14.2 nmor 3.18.1 has OSGI support for that.
>
> Also missing in Camel 3.18.1 is the OSGI support of MongoDB, which still
> exists in 3.14.
>
> Also using CDI is quite confusing for me. Aries, Blueprint, Pax CDI,
> Camel-CDI... so many combinations... @Service, @OsgiServiceProvider,
> @Inject, @Reference... so many annotations, some of which are apparently
> deprecated. Currently we are using weld in our monolith: weld-se-shaded,
> deltaspike-cdictrl-weld with Camel-CDI.
>
> Overall, many (all?) tutorials and examples seem to be very outdated: I
> rarely find examples from 2020 or later. Apparently, even after 2020, so
> much has changed at Camel. Maybe you can point me to one or the other
> problem where I can get current information: OSGI-Mongo-Support, CDI,
> camel-endopointsdsl...
>
> With kind regards
> Bert Speckels
>

As a recipient of an email from Talend, your contact personal data will be on 
our systems. Please see our privacy notice. <https://www.talend.com/privacy/>


Reply via email to