Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
MIME-Version: 1.0
In-Reply-To: <4A1466B8-BDD2-4AF6-BE95-9AF551321919@stefanutti.fr>
References: <CAA8i-pZH52YAfC6iEtP3_ySicO-7n8mWt0qaEPK+Q+2w3NcmTg@mail.gmail.com>
 <4A1466B8-BDD2-4AF6-BE95-9AF551321919@stefanutti.fr>
From: Brad Johnson <brad.johnson@mediadriver.com>
Date: Mon, 8 Aug 2016 08:23:41 -0500
Message-ID: <CAA8i-pZR_41EAwzY7H95zHiCN7sBoXtODoKqpHups0cojHTpyg@mail.gmail.com>
Subject: Re: CDI before Camel 2.17?
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=001a114e6e582d081b05398f535a
archived-at: Mon, 08 Aug 2016 13:23:50 -0000

--001a114e6e582d081b05398f535a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Excellent. That's pretty much what I'm looking for since I recognize it is
a matter of evolving toward that and not needing to jump into it whole hog.

I can probably live with CamelTestSupport with out the CDI runner for the
time being as well.  Part of the problem is the underlying mechanisms
aren't obvious to me since I've been using Spring and then Blueprint for so
long and I've  pretty much always gone with hand wiring of internals.

I'm not sure where the future is going with Blueprint, DS, SCR, CDI, Spring
Boot, Delta Spike, etc. but the Camel RouteBuilder will be germane in all
situations and for now I'm using Blueprint for very basic bootstrap.

While I commonly use OSGi services and export and reference them from my
bundles, to be honest I could live without them if necessary.  I mean the
great benefit for me in using OSGi with Camel is the classloader
segregation and ability to hide internal classes in a bundle.  But I can
always run routes between bundles to accomplish much the same thing that
service provide and, in a way, it is more portable.

But the ease of wiring that CDI provides is compelling and I'm very excited
about that future.

On Mon, Aug 8, 2016 at 4:21 AM, Antonin Stefanutti <antonin@stefanutti.fr>
wrote:

> Hi Brad,
>
> The examples (camel-example-cdi.*) that are available in
> https://github.com/apache/camel/tree/master/examples should work to some
> great extent in Camel versions prior to 2.17.0.
>
> As these examples concentrate on the non-advanced features and the new
> version of Camel CDI introduced in 2.17.0 managed to be largely backward
> compatible, these should work in prior versions with some little adaptati=
on.
>
> You can find some more details about these non backward compatible change=
s
> in https://issues.apache.org/jira/browse/CAMEL-9201 and
> http://camel.apache.org/camel-2170-release.html.
>
> For testing, Camel CDI test won't be available, though you can use plain
> Arquillian testing support. You can find more info in
> http://camel.apache.org/cdi-testing.html.
>
> If that=E2=80=99s not enough for you to wait until Camel 2.17 / Fuse 6.3,=
 let me
> know and we=E2=80=99ll try to help you further.
>
> Antonin
>
> > On 06 Aug 2016, at 00:30, Brad Johnson <brad.johnson@mediadriver.com>
> wrote:
> >
> > Are there any good examples of how to use CDI with Camel before 2.17?
> > Obviously that's a better option to go with and when the Fuse 6.3 relea=
se
> > hits it's first milestone that's what I'll go to but until then I can u=
se
> > Camel 2.17 CDI test but have to use the older features with Fuse 6.2.1.
> >
> > Unless there's a patch or upgrade that does this already?
> >
> > Brad
>
>

--001a114e6e582d081b05398f535a--