Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of james.strachan@gmail.com
 designates 64.233.184.232 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=V1ei1d4nbp9DaSsI9AVfRYE67TZtwfOVJo6jkrUX4lv9sGZx+OMPePOMK8OULTnl5h
         IVOCwWK3XX/OsS/zzB9ZJaq/9BgMHivyq+/zgojsDE8cZTTyatUuZeDWLUHUsjXlMufB
         vGQy1VhdRHKEIGbqSd8EFDZ2fKqgdyJXcW448=
Message-ID: <ec6e67fd0807230543l497e9d99sf1c0447a869a798e@mail.gmail.com>
Date: Wed, 23 Jul 2008 13:43:29 +0100
From: "James Strachan" <james.strachan@gmail.com>
To: camel-user@activemq.apache.org
Subject: Re: Celebrating Camel 1.4.0 release - New Tutorial - Feedback
 appreicated
In-Reply-To: <4C1FB9C00D24A140906239533638C4D204DBA12D@EXVS04.exserver.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <4C1FB9C00D24A140906239533638C4D204DBA12D@EXVS04.exserver.dk>

Great stuff Claus! I've finally got time to read the whole thing, good job!

One real minor point with part 2...
http://activemq.apache.org/camel/tutorial-example-reportincident-part2.html

you can replace this code...
  // get the log component
            Component component =3D camel.getComponent("log");

            // create an endpoint and configure it.
            // Notice the URI parameters this is a common pratice in
Camel to configure
            // endpoints based on URI.
            // com.mycompany.part2 =3D the log category used. Will log
at INFO level as default
            Endpoint endpoint =3D
component.createEndpoint("log:com.mycompany.part2");

with just

            Endpoint endpoint =3D camel.getEndpoint("log:com.mycompany.part=
2");

which under the covers will do the same thing; resolving the component
and asking it to create the endpoint etc. No biggie though; its maybe
nice seeing how to do things by hand before the camel magic takes over
etc.

I was wondering if we could add a Part 4 at some point where we try
and hide more of the Camel APIs from the application code; using the
bean integration stuff more to do the heavy lifting without requiring
any of the Camel APIs (other than a few annotations here or there)
http://activemq.apache.org/camel/bean-integration.html

Ideally it'd be good if developers wrote POJOs with some annotations;
then the camel route binds things together; with the main Java code
not being dependent on any middleware specific APIs etc.


2008/7/22 Claus Ibsen <ci@silverbullet.dk>:
> Hi
>
> Camel 1.4.0 has finally been voted for release.
>
> To celebrate this great event I have written a new tutorial, that is insp=
ired by a real life use-case and how it can be implemented with Camel.
>
> The tutorial is target for end-users with no to medium knowledge of Camel=
. It's very different from what we else have, since it's focused on how you=
 can bring in Camel to an existing solution and it's focused on using the J=
ava building blocks that Camel also internally uses for endpoints, producer=
s and consumers etc.
>
> I plan to continue the tutorial, but at this point I would love some feed=
back. It does after all take quite some time to write.
>
> I was inspired by a phone call from a colleague and my local development =
team that will think Camel is a bit to "magic" and get off by it, if they c=
an't fell they are in control and slowly grasp Camel.
>
> Throwing annotations, spring xml files, AOP and Java DSL routes in their =
face would not be the way to introduce Camel for a development team with st=
rong roots in traditional J2EE development with EJBs and heavy platforms.
>
> Feedback appreciated. Tutorial is at:
> http://activemq.apache.org/camel/tutorial-example-reportincident.html
>
> If for some reason the static HTML pages isn't displaying correctly, the =
dynamic site is here:
> http://cwiki.apache.org/confluence/display/CAMEL/Tutorial-Example-ReportI=
ncident
>
> I do think on the static HTML part 1 the 4 images isn't displayed.
>
>
> Med venlig hilsen
>
> Claus Ibsen
> ......................................
> Silverbullet
> Skovsg=E5rdsv=E6nget 21
> 8362 H=F8rning
> Tlf. +45 2962 7576
> Web: www.silverbullet.dk
>
>


--=20
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://open.iona.com