activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <>
Subject Re: [HeadsUp] Camel library for POJO based routing...
Date Tue, 20 Mar 2007 10:47:02 GMT
On 3/20/07, Guillaume Nodet <> wrote:
> Sounds good.
> I will try to see how it fits with ServiceMix ...
> There are a few problems that may need some changes.
> For example, support for different MEPs: JBI defines strict
> meps (InOnly, InOut, etc...) that need to be known when the
> exchange is created, so I guess we will need an additional
> parameter when creating the exchange to specify if we expect
> a response or not ....

Yeah, we might need to have a few different createExchange() methods
on some endpoints (like JBI or CXF). One of the things I hoped was
that we can have typesafe exchange and endpoints to totally expose the
full features of the underlying bus. e.g. JbiExchange and JbiEndpoint
should expose all of the JBI APIs; ditto for Http, CXF, JMS etc. For
JBI in particular but also for CXF too; there's the added complexity
of fitting in with the component/endpoint container & lifecycle model
though am sure we can get that working given time

Though I'm pretty confident though we'll find some gremlins along the
way as we try use Camel in ServiceMix, CXF or Servlets :). The one
thing in our favour though is the Exchange and Endpoint types are
pretty vague and pluggable, so I'm sure we can come up with, say, a
JBI specific exchange API which works great with JBI - then once we've
got a few endpoints that support InOut/InOnly we can see if we can
pull a bit more stuff back into the Camel core.

> More feedback will follow ...
> On 3/19/07, James Strachan <> wrote:
> >
> > While hungover and stuck on a train I hacked up a little POJO library
> > I've wanted for a while - an easy way to route stuff around JMS using
> > a simple Java DSL and ultimately for easily creating Enterprise
> > Integration Patterns in pure Java...
> >
> >
> >
> >
> > its still very much work in progress though!  The basic idea is to use
> > Java rather than XML (shock horror!) for creating routing rules and to
> > use generics to make it easy to work with JMS messages directly or to
> > work with other kinds of message like HTTP, JBI or JAX-WS etc
> >
> > I'm still tinkering with it to get the JMS stuff working nicely.  I've
> > kept the JMS stuff separate (in camel-jms) so that the camel-core.jar
> > has minimal dependencies so hopefully we might be able to reuse this
> > library on other projects like ServiceMix and CXF
> >
> > Ultimately I'd like to make it easy to drop JMS routes on the
> > classpath which could be automatically embedded in the broker, or
> > enabled in any Spring XML file to simplify the JMS processing for end
> > users.
> >
> > I'll post more details as things start to settle down...
> >
> > As usual, feedback greatly appreciated!
> > --
> >
> > James
> > -------
> >
> >
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (
> Blog:



View raw message