Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
From: Antonin Stefanutti <antonin@stefanutti.fr>
To: "users@camel.apache.org" <users@camel.apache.org>
Subject: Re: State of the camel-cdi component
Thread-Topic: State of the camel-cdi component
Thread-Index: AQHRRx8WhYgy8HjA6UmRqysQYULCMJ7ro6WA
Date: Mon, 4 Jan 2016 18:55:14 +0000
Message-ID: <FE459677-46A5-4E85-9973-6A0D214502C4@stefanutti.fr>
References: <1418311024131-5760578.post@n5.nabble.com>
 <CAAxZHdf5zod9AOFNmo5tgeTYsau4G2kfH88oEKy3ejH02pwa1g@mail.gmail.com>
 <568ABBDB.7080101@gmail.com>
In-Reply-To: <568ABBDB.7080101@gmail.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [88.182.187.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0E70492893E83B428249DA103C5B4176@indiv.local>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Ovh-Tracer-Id: 13826050858191725786
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: 0
X-VR-SPAMCAUSE: 
 gggruggvucftvghtrhhoucdtuddrfeekiedrieejgdduudekucetufdoteggodftvfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecu

Hi Tim,

We are actively working on improving the Camel CDI integration for the upco=
ming 2.17.0 release. This is followed-up in https://issues.apache.org/jira/=
browse/CAMEL-9201.

That will be essentially the merging of the work being done in https://gith=
ub.com/astefanutti/camel-cdi.

This will bring, among other things, better CDI programming model integrati=
on plus the portability to all targeted runtimes (Java SE, servlets contain=
ers, Java EE, OSGi with the expositing of the CDI camel contexts as OSGi se=
rvices) and implementations (Weld and OpenWebBeans).

In the meantime, you can use the version in https://github.com/astefanutti/=
camel-cdi as a drop-in replacement and switch back to the official one once=
 that gets merged and released into the official component.

Antonin

> On 04 Jan 2016, at 19:37, Tim Dudgeon <tdudgeon.ml@gmail.com> wrote:
>=20
> Hi,
>=20
> Was wondering what the latest status was here (read below)?
> I'm trying to adapt a camel-servlet app to use CDI and it's not clear how=
 to best go about this.
>=20
> Thanks
>=20
> Tim
>=20
> On 11/12/2014 16:07, Charles Moulliard wrote:
>> Hi Jason,
>>=20
>> I'm working with Antonin on that new camel-cdi. when the code will be re=
ady
>> it will be integrated with Camel project
>>=20
>> Regards,
>>=20
>> On Thu, Dec 11, 2014 at 4:17 PM, Jason Holmberg <holmbrew@gmail.com> wro=
te:
>>=20
>>> Will the Camel project will officially adopt:
>>>=20
>>> https://github.com/astefanutti/camel-cdi
>>>=20
>>> as its CDI extension.  I have experimented with the 'official' extensio=
n
>>> available in 2.14.0 and feel that it is lacking much of what it needs t=
o a
>>> viable component where as https://github.com/astefanutti/camel-cdi seem=
s
>>> to
>>> have addresses many if not all of the deficiencies.
>>>=20
>>> I see that there is active development on the official camel-cdi compon=
ent,
>>> I feel that the work being done in
>>> https://github.com/astefanutti/camel-cdi
>>> is looking and working really well.
>>>=20
>>> We would really prefer CDI over Spring for DI.
>>>=20
>>> Thanks,
>>> Jason
>>>=20
>>>=20
>>>=20
>>> --
>>> View this message in context:
>>> http://camel.465427.n5.nabble.com/State-of-the-camel-cdi-component-tp57=
60578.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>=20
>>=20
>>=20
>=20