camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <boa...@gmail.com>
Subject Re: Camel in Action Book
Date Sat, 17 Sep 2016 17:08:09 GMT
Claus always mentions it in the release vote threads. It's a good code
sample that's easy to test against without having to test out some overly
complicated enterprise app to find every nook and cranny.

On 17 September 2016 at 12:05, Brad Johnson <brad.johnson@mediadriver.com>
wrote:

> Matt,
>
> That's interesting.  I didn't know the code was tested against each new
> release.  Makes sense though.  Most of what I've seen over the years has
> been (a) added features, (b) bug fixes, and (c) performance enhancements.
> And of course the ever growing library of components.
>
> On Sat, Sep 17, 2016 at 12:02 PM, Matt Sicker <boards@gmail.com> wrote:
>
> > All the code samples from CiA are tested against each release, so they
> all
> > still work. There's a lot of new components since 2.5, but the basic DSL
> > remains the same.
> >
> > On 17 September 2016 at 11:59, medali_k <mkhemila@icloud.com> wrote:
> >
> > > I am trying to learn Camel from the book 'Camel in Action'. The current
> > > edition of the book uses Camel 2.5 while Camel is now at version 2.17.
> I
> > > need help with these questions:
> > > 1/ Is there a big difference between the 2 versions?
> > > 2/ If I complete the book, what kind of other resources/subjects
> should I
> > > look at in order to update myself to the newer versions of Camel?
> > > Note that I don't have time to wait for the new edition of the book,
> > > apparently scheduled to be released in March 2017.
> > > Many thanks for helping!!
> > >
> > >
> > >
> > > --
> > > View this message in context: http://camel.465427.n5.nabble.
> > > com/Camel-in-Action-Book-tp5787674.html
> > > Sent from the Camel - Users mailing list archive at Nabble.com.
> > >
> >
> >
> >
> > --
> > Matt Sicker <boards@gmail.com>
> >
>



-- 
Matt Sicker <boards@gmail.com>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message