On Thu, Oct 7, 2010 at 3:51 PM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: > As promised, here's my take [1] on the getIn()/getOut() confusion. > In a few days, when the dust will settle I'll take what's relevant from the > post, and the comments that will follow and update the wiki page. > > I hope that clarifies the issue better, > Hadrian > > [1] http://camelbot.blogspot.com/2010/10/should-you-getin-or-getout.html >
Hadrian this is a nice piece of writing you did. Love to see the improved documentation at Apache which should be the result of this. Remember to update the javadoc on Exchange as well. I would also suggest adding some link or info to the FAQ from the "Getting Started" guides somewhere, in case the end user starts playing with a Processor, and thus gets exposed to the Exchange and the question on the getIn and getOut methods. > > On Oct 4, 2010, at 3:58 PM, Mark Webb wrote: > >> I agree. But when producing an out I think you need to call >> Exchange.setIn(Message). Seems like when you call >> Exchange.setOut(Message) you are setting up a request-reply scenario >> which is not what I wanted. >> >> >> On Mon, Oct 4, 2010 at 1:54 PM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: >>> Yeah, there is still a lot of confusion. >>> Unfortunately that page is bollocks and I'll have to get it cleaned up. >>> Mark, I think you did the right thing actually, in a processor one should >>> *not* modify the in, but produce an out, if needed. It's time to get that >>> clarified! >>> >>> My $0.02, >>> Hadrian >>> >>> On Oct 4, 2010, at 10:01 AM, Claus Ibsen wrote: >>> >>>> On Mon, Oct 4, 2010 at 3:57 PM, Mark Webb <elihusma...@gmail.com> wrote: >>>>> Thanks. I have things working now. >>>>> >>>>> It seems weird to me though that if in a Processor I take a message >>>>> in, transform it into a newly created Message object that I should >>>>> call Exchange.setIn(Message) instead of Exchange.setOut(Message). I >>>>> think of a Processor as taking "in" a message and then sending it >>>>> "out", but it looks like that is not the case. Just need to adjust >>>>> the way I think about things. >>>>> >>>> >>>> You are not the only one. See this FAQ >>>> http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html >>>> >>>>> >>>>> >>>>> On Sat, Oct 2, 2010 at 3:06 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: >>>>>> See this FAQ >>>>>> http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html >>>>>> >>>>>> On Fri, Oct 1, 2010 at 10:37 PM, Mark Webb <elihusma...@gmail.com> wrote: >>>>>>> I am sending messages through a Camel route in ActiveMQ. My message >>>>>>> reaches the end of the processing chain, and at the last processor I >>>>>>> call exchange.setOut( newly created DefaultMessage ). When I look at >>>>>>> the admin page for ActiveMQ, the topic shows that there is a message >>>>>>> to be dequeued. It even says that there is a consumer connected to >>>>>>> that topic, which is a GUI tool I wrote. The GUI tool makes a call to >>>>>>> Consumer.setMessageListener. So why are the messages not making their >>>>>>> way to my GUI tool? I am stumped as to why the messages sit in the >>>>>>> topic and never leave if there is a listener for that topic. >>>>>>> >>>>>>> Of course the first thought is, is the Connection started? Yeah I >>>>>>> verified that. In fact I can send messages to the topic via the >>>>>>> web-based admin tool for ActiveMQ and the GUI receives them. >>>>>>> >>>>>>> Thanks for any help you have, >>>>>>> Mark >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Claus Ibsen >>>>>> Apache Camel Committer >>>>>> >>>>>> Author of Camel in Action: http://www.manning.com/ibsen/ >>>>>> Open Source Integration: http://fusesource.com >>>>>> Blog: http://davsclaus.blogspot.com/ >>>>>> Twitter: http://twitter.com/davsclaus >>>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Claus Ibsen >>>> Apache Camel Committer >>>> >>>> Author of Camel in Action: http://www.manning.com/ibsen/ >>>> Open Source Integration: http://fusesource.com >>>> Blog: http://davsclaus.blogspot.com/ >>>> Twitter: http://twitter.com/davsclaus >>> >>> > > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
