camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <christian.muel...@gmail.com>
Subject Re: Apache Camel - war project How to process the Queue and set to another queue?
Date Thu, 03 Oct 2013 21:44:57 GMT
Maybe
from
  bean

is a valid route...

Best,
Christian
Am 03.10.2013 17:46 schrieb "James Carman" <james@carmanconsulting.com>:

> That second route with no "to" is "stealing" your messages, I'd guess.
>  I am actually surprised you're able to create a route with no "to."
> I'm curious to play with that phenomenon in a test case.
>
> On Thu, Oct 3, 2013 at 11:36 AM, Andreas Gies <andreas@wayofquality.de>
> wrote:
> > Hi,
> >
> > it might be me, but I think your 2nd route is missing a to-element.
> > You need to do something with message like drop it to a file or at least
> log
> > it.
> >
> > Otherwise, like others have pointed out, using beans as payload is bad
> > practice
> > in integration applications. However, you seem to be happy with that ...
> >
> > Best regards
> > Andreas
> >
> >
> > On 09/30/2013 12:44 PM, kosalads wrote:
> >>
> >> I have done a small app which connect to the camel war and do the
> >> processing
> >> and set to another queue. However, when I process sample xml files it
> does
> >> goes to the relevant queues and process. Unfortunately, when I use Bean
> >> Object via camel It doesnt get updated in the 2nd queue.
> >>
> >> If I explain bit more , This is how I have configured in the application
> >> context which is in the camel war deployed in Jetty server.
> >>
> >>
> >>      <camelContext xmlns="http://camel.apache.org/schema/spring">
> >>          <route>
> >>              <from uri="activemq:inQ" />
> >>              <to uri="activemq:outQ" />
> >>          </route>
> >>      </camelContext>
> >>
> >>      <bean id="activemq"
> >> class="org.apache.activemq.camel.component.ActiveMQComponent">
> >>          <property name="brokerURL" value="tcp://localhost:61616" />
> >>      </bean>
> >>
> >>           <camelContext xmlns="http://camel.apache.org/schema/spring">
> >>          <route>
> >>              <from uri="activemq:outQ" />
> >>          </route>
> >>      </camelContext>
> >>
> >> I have crated three applications.
> >>
> >> 1. Standalone application which connect to the camel war and send the
> Pojo
> >> Class to the Queue (inQ).
> >> 2. Camel war application which has above configuration. So when I pass
> the
> >> Bean Object to the inQ it should send to the outQ
> >>     (Based on above configuration)
> >> 3. There is another application which reads the outQ and try to retrieve
> >> Bean Object.
> >>
> >> So what happens is that I could send the Pojo bean to the inQ but it
> >> doesnt
> >> seems to be route to the outQ. So when I try to read from the outQ the
> >> queue
> >> is empty.
> >>
> >> Could you please let me know how we can handle above scenario and what
> is
> >> the best way to handle this.
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://camel.465427.n5.nabble.com/Apache-Camel-war-project-How-to-process-the-Queue-and-set-to-another-queue-tp5740524.html
> >> Sent from the Camel - Users mailing list archive at Nabble.com.
> >>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message