Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (herse.apache.org: domain of paul.dlug@gmail.com designates
 209.85.132.244 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=DsWZjM6nfoVVURExK7pG3+ytdbWkIozii94B+r64se/jvBYFdo5gz8/UjfDyVEyrD2ZQ+PbPl/HBR/rFwveoLoxImZlXF8U+3NAifBQAEDr0WKfjZRkX0mbQu4NK+rRjAJIKJqEjNcZp8nC7C5HS1nrZW4cIJmuKU6kF3yWgAdU=
Message-ID: <a1bf48f10707051251p1fa35a83y8f3655cbcf7e7cd4@mail.gmail.com>
Date: Thu, 5 Jul 2007 15:51:22 -0400
From: "Paul Dlug" <paul.dlug@gmail.com>
To: camel-user@activemq.apache.org
Subject: Re: Appropriate use case for Camel?
In-Reply-To: <ec6e67fd0707031116k479ac1c5h42bd67121b2f3efc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <a1bf48f10707030824j6ea22b8w78e49a36725914e5@mail.gmail.com>
	 <ec6e67fd0707030857n7a9e3815i8a9a18b5ad7e4fe6@mail.gmail.com>
	 <ec6e67fd0707031038k5225929cie426937acc1df7ec@mail.gmail.com>
	 <a1bf48f10707031046x570d0fcy7bf869e39b1cbbed@mail.gmail.com>
	 <ec6e67fd0707031116k479ac1c5h42bd67121b2f3efc@mail.gmail.com>

On 7/3/07, James Strachan <james.strachan@gmail.com> wrote:
> On 7/3/07, Paul Dlug <paul.dlug@gmail.com> wrote:
> > On 7/3/07, James Strachan <james.strachan@gmail.com> wrote:
> > > On 7/3/07, James Strachan <james.strachan@gmail.com> wrote:
> > > > On 7/3/07, Paul Dlug <paul.dlug@gmail.com> wrote:
> > > > > Hopefully this is an easy answer. I'm a bit unclear on how Camel
> > > > > should actually be used. I'm currently using ActiveMQ to do some basic
> > > > > integration between applications in Java, Ruby, Perl, primarily via
> > > > > STOMP. I'd like to use Camel to apply some of the enterprise
> > > > > integration patterns, especially as it applies to routing as well as
> > > > > using some of the built in connectors. From a quick read through the
> > > > > docs it appears that I need to build Camel into an application itself
> > > > > (in a servlet container or via spring). Is it possible to just run
> > > > > Camel inside an ActiveMQ server to configure queues and handle routing
> > > > > and other patterns?
> > > >
> > > > Absolutely! Actually its on my list of things to do to provide some
> > > > examples of how to drop camel into the activemq.xml file.
> > >
> > > Actually it turned out to be way easier than I thought!
> > >
> > > http://cwiki.apache.org/ACTIVEMQ/enterprise-integration-patterns.html
> > >
> > > So you could just download tomorrows 5.0 snapshot and you're good to go...
> >
> > Thanks James! I've been building 5.0 from subversion anyway so I just
> > updated my local copy and I'll give this a shot.
>
> Great! Let us know how you get on & if there's anything we can do to
> make it easier to use Camel from inside the ActiveMQ broker

Perhaps I'm still a bit unclear on how to use this, I specified the
following config:

  <camelContext id="camel"
xmlns="http://activemq.apache.org/camel/schema/spring">
    <route>
      <from uri="queue:a"/>
      <to uri="queue:b"/>
    </route>
  </camelContext>

Which as I understand it should take messages addressed to the queue
"a" and send them to "b". This doesn't seem to actually work though,
I've tried changing the endpoints from "queue:a" to "activemq:a" but
that didn't seem to help. Any tips for a newbie?

Another question I have is, how do I reload new definitions without
restarting? I've I'd like to change destinations or filtering how can
I do that on the fly and be sure I'm not dropping any messages?


Thanks,
Paul