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 .... More feedback will follow ...
On 3/19/07, James Strachan <[EMAIL PROTECTED]> 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... http://cwiki.apache.org/CAMEL/routes.html http://cwiki.apache.org/CAMEL/eip.html 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 ------- http://radio.weblogs.com/0112098/
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
