Hi
I created a ticket for this issue
https://issues.apache.org/activemq/browse/CAMEL-1563
On Sun, Apr 19, 2009 at 8:53 PM, Roman Kalukiewicz
wrote:
> 2009/4/18 Claus Ibsen :
>> We could add boolean hasOut() as a method on the Exchange.
>> Then you can test whether an OUT has been set or not.
>
On Sun, Apr 19, 2009 at 8:53 PM, Roman Kalukiewicz
wrote:
> 2009/4/18 Claus Ibsen :
>> We could add boolean hasOut() as a method on the Exchange.
>> Then you can test whether an OUT has been set or not.
>>
>> even though getOut(false) does exactly that. Returning null if no OUT exists.
>
> This is
2009/4/18 Claus Ibsen :
> We could add boolean hasOut() as a method on the Exchange.
> Then you can test whether an OUT has been set or not.
>
> even though getOut(false) does exactly that. Returning null if no OUT exists.
This is not my point, that there is no clear way of verifying if there
is o
thod would return null. I finally narrowed it down to the
>>>> exchange.getOut().setHeader() method, which I have listed below. If I
>>>> comment out that line, the next processor can get the inbound body. Why
>>>> would setting a header in the outbound me
ocessor can get the inbound body. Why
>>> would setting a header in the outbound message affect the inbound message?
>>> Am I doing something wrong?
>>>
>>> ...
>>> process(new Processor() {
>>> public void process(Exchange exchange) throws Exception {
>>>
t; public void process(Exchange exchange) throws Exception {
>> ...
>> exchange.getOut().setHeader("foo", "bar");
>> ...
>> }
>> }).to("seda:next");
>>
>> Thanks,
>> Joe
>>
>
nge) throws Exception {
> ...
> exchange.getOut().setHeader("foo", "bar");
> ...
> }
> }).to("seda:next");
>
> Thanks,
> Joe
>
> --
> View this message in context:
> http://www.nabble.com/Payload-Gets-Nulled-Out-tp23105477p23105477.html
> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
>
>
void process(Exchange exchange) throws Exception {
...
exchange.getOut().setHeader("foo", "bar");
...
}
}).to("seda:next");
Thanks,
Joe
--
View this message in context:
http://www.nabble.com/Payload-Gets-
