Taking Apache Camel for a Ride with Bruce Snyder

camel is a java api that allows you to do message routing very easily. it implements many of the patterns found in enterprise integration patterns . it doesn't require a container and can be run in any java-based environment. camel has a whole bunch of components - bruce is showing a 6 x 10 grid with a component name in each grid. in other words, there's 60 components that camel can use. examples include: activemq, sql, velocity, file and ibatis.

chris richardson asks "what's left inside of servicemix". why use servicemix if you have camel? servicemix is a container that can run standalone or inside an app server. you can run distributed servicemix as a federated usb. camel is much smaller and lightweight and is really just a java api. servicemix 4 changed from a jbi-based architecture to osgi (based on apache felix). they also expect to create your routes for servicemix 4 with camel instead of xml. to process messages, you can use many different languages: beanshell, javascript, groovy, python, php, ruby, jsp el, ognl, sql, xpath and xquery.

camel has a camelcontext that's similar to spring's applicationcontext . you can initialize it in java and add your routes to it:

camelcontext context = new defaultcamelcontext();
context.addroutes(new myrouterbuilder());
context.start();

or you can initialize it using xml:

<camelcontext xmlns="http://activemq.apache.org/camel/schema/spring">
    <package>com.acme.routes</package>
</camelcontext>

camel's routebuilder contains a fluid api that allows you to define to/from and other criteria. at this point, bruce is showing a number of examples using the java api. he's showing a content based router, a message filter, a splitter, an aggregator, a message translator, a resequencer, a throttler and a delayer.

bruce spent the last 10 minutes doing a demo using eclipse, m2eclipse, the camel-maven-plugin and activemq. it's funny to see a command-line guy like bruce say he can't live w/o m2eclipse. i guess maven's xml isn't so great after all.

camel is built on top of spring and has good integration. apparently, the camel developers tried to get it added to spring, but the springsource guys didn't want it. coincidentally, spring integration was released about a year later.

camel also allows you to use "beans" and bind them to camel endpoints with annotations. for example:

public class foo {

    @messagedriven (uri="activemq:cheese")
    public void oncheese(string name) {
        ...
    }
}

other annotations include @xpath, @header and @endpointinject.

camel can also be used for bam (business activity monitoring). rather than using routebuilder, you can use activitybuilder to listen for activities and create event notifications.

bruce had quite a few folks show up for this presentation. i had trouble finding a seat because i was late. i think he did a good job of showing what camel is and how you might use it.

from http://raibledesigns.com