camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Franz Paul Forsthofer <>
Subject Re: To CXF experts: Setting of SOAP headers via the Camel Header "org.apache.cxf.headers.Header.list" for CXF data format "PAYLOAD"
Date Mon, 27 Jul 2015 11:21:59 GMT
Hi Aki,

there will be no change to the old behavior. Suppose you have the
following scenario: A SOAP client sends to a CAMEL CXF consumer and
this consumer just forwards the message to a Camel CXF provider which
calls a receiver SOAP server. If the SOAP client sends a SAP Header
then this header will also be forwarded to the CXF provider which just
forwards the header to the SOAP server. This happened before the patch
and the same will happen after the patch.

Regards Franz

On Fri, Jul 24, 2015 at 4:27 PM, Aki Yoshida <> wrote:
> Hi Franz,
> I wanted to look at this but had not had time and a little late to comment.
> One question or concern that I had wasthat this would change the
> behavior of the existing tunneling scenarios using some soap headers,
> no?
> In other other words, some unwanted headers might tunnel through and
> show up at the other end?
> thanks.
> regards, aki
> 2015-07-21 12:44 GMT+02:00 Franz Paul Forsthofer <>:
>> Hi,
>> can I assume that there are no objections against the patch I proposed
>> in
>> Best Regards Franz
>> On Fri, Jul 17, 2015 at 10:02 AM, Franz Paul Forsthofer
>> <> wrote:
>>> Hi,
>>> Accessing the SOAP headers via the Camel header
>>> "org.apache.cxf.headers.Header.list" after a CXF consumer works fine,
>>> also for the CXF data format "PAYLOAD".
>>> However, currently the setting of SOAP headers via the Camel header
>>> "org.apache.cxf.headers.Header.list" is not working for a CXF producer
>>> with  CXF data  format "PAYLOAD".
>>> I found out that the list value contained in Camel header
>>> "org.apache.cxf.headers.Header.list"  is correctly forwarded to the
>>> CXF request, however in the CxfEndpoint.CamelCxfClientImpl this list
>>> is overwritten by the value CxfPaylaod.getHeaders().
>>> Therefore I propose  to merge the values from the Camel header
>>> "org.apache.cxf.headers.Header.list" with the values of
>>> CxfPaylaod.getHeaders(). This has the advantage that you can set the
>>> headers either via the CxfPayload or by the Camel header
>>> "org.apache.cxf.headers.Header.list".
>>> For more details have a look at
>>> Can somebody of the CXF experts comment whether my solution is
>>> feasible. Then I will commit the patch.
>>> Best Regards
>>> Franz Forsthofer

View raw message