If you switch the data format to POJO, you should not see the security header any more. If you still need to use PAYLOAD data format, you need to clean up the soap header of the payload message, as camel-cxf doesn’t put the soap header into camel message header.
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On July 7, 2014 at 6:48:34 AM, Michael Lambert (macfleck...@functionofwhy.com) wrote: > I am attempting to proxy calls to a service and centralize ws-secuity > handling within a camel route. Everything works perfectly but the > ws-secuirty headers arent being removed and are instead being propogated > down to the proxied service. This results in a MustUnderstand problem as > the proxied service is not setup to handle security. > > This has to be a common scenario. Can someone give me a hint as to what > might be wrong? > > The cxf endpoints are configured this way: > > ---- > > address="/proxy/userService" > endpointName="us:userSoapServicePort" serviceName="us:userSoapServicePorts" > wsdlURL="classpath:service/user-soap-v1.wsdl" > xmlns:us="urn:healthmedia:wsdl:user:soap:v1" > > > > > > value="classpath:server-keystore.properties" /> > > > > > > address="${user-service.url}" > endpointName="us:userSoapServicePort" serviceName="us:userSoapServicePorts" > wsdlURL="classpath:service/user-soap-v1.wsdl" > xmlns:us="urn:healthmedia:wsdl:user:soap:v1" /> > > ---- > And the route is configured this way: > ---- > > > > location="classpath:user-service.properties"/> > > > > > > > > > > > > > > ---- > > Thanks in advance! > > -Mike >
