Hi Sergey Not sure, in my case I explicitly tell Camel not to delegate the soap headers but it does.
Thanks Oli ________________________________________ From: Sergey Beryozkin [sberyoz...@gmail.com] Sent: 06 February 2014 15:35 To: users@camel.apache.org Subject: Re: CxfHeaderFilterStrategy doesn't drop SOAP headers Hi Oli I think it is exactly the same side-effect which was reported by one of CXFRS users: https://issues.apache.org/jira/browse/CAMEL-6865 I believe this is configurable, but can be rather unexpected all right... Sergey On 06/02/14 14:25, Oliver Wulff wrote: > Hi there > > I've created the following Camel route: > > <bean id="dropAllMessageHeadersStrategy" > class="org.apache.camel.component.cxf.common.header.CxfHeaderFilterStrategy"> > <!-- Set relayHeaders to false to drop all SOAP headers --> > <property name="relayHeaders" value="false"/> > </bean> > > <camelContext xmlns="http://camel.apache.org/schema/spring";> > <route> > <from > uri="cxf:bean:proxyCRMEndpoint?headerFilterStrategy=#dropAllMessageHeadersStrategy"/> > <to uri="cxf:bean:targetCRMEndpoint"/> > </route> > </camelContext> > The data format is CXF_MESSAGE. > > This should drop the incoming SOAP headers. The cxf component which produces > the message for the target web services request a new token from the STS. But > this message contains then a WS-Security header with two SAML assertions and > two Timestamp elements because the incoming headers are not dropped. > > I use Camel version 2.10.4 in Karaf. > > Am I doing anything wrong? > > Thanks > Oli > >
