+1 for getMessage() :)
On Mon, Feb 17, 2020 at 11:18 AM Giovanni Condello <
giovanni.conde...@coderit.it> wrote:
> Hi Marci,
>
> to add on what Alex said, I found it's always better to use either
> getMessage() or to explicitly check if the exchange hasOut() instead of
> assuming getIn() is alway
Hi Marci,
to add on what Alex said, I found it's always better to use either getMessage()
or to explicitly check if the exchange hasOut() instead of assuming getIn() is
always the right place to look for data coming out of a component
Giovanni
-Messaggio originale-
Da: Alex Dettinger
Hi Marci,
I would say that from("jms:Sahara")... has MEP InOUt so In
message with header "foo",
and OUT message with header "bar".
So assertThat(“return should be
bar”,reply.get*Out/Message*().getHeader(“test”),equalTo(“bar”)
should be ok.
Alex
On Mon, Feb 17, 2020 at 11:02 AM Alex Dettinge
Hi Marci,
I would say that from("jms:Sahara")... has MEP InOUt so In
message with header "foo",
and OUT mess
On Fri, Feb 14, 2020 at 11:43 PM Marci wrote:
>
> I understand that the new Processor(){} is for the message being sent to
> the consumers (from(route)) and this is working fine.
> Wh
