2 Replies Latest reply on Nov 3, 2013 4:35 PM by Lekkie Omotayo

    Cleaner way to compose web services than setHeader (operationName & operationNamepace)?

    Roy Brumby Newbie

      Hi - I need to provide a SOAP service which calls multiple other SOAP services, with transformations from the input service to the inputs of the services being orchestrated.

      I'm using blueprint. eg.

      <from uri="cxf:bean:..."/>

      <to uri="xslt://..."/>

      <setHeader headerName="operationName">
           <constant>ws1Op</constant>
      </setHeader>
      <setHeader headerName="operationNamespace">
           <constant>http://ws1OpNS</constant>
      </setHeader>

      <to uri="cxf:bean:ws1Bean..."/>

      ...more setHeaders here...

      <to uri="cxf:bean:ws2Bean..."/>

       

      This is working - but it's the only way I have managed to get this to work. All these setHeader's everywhere is pretty messy.

      I have tried setting endpointName as options to the "cxf:bean:..." and as attributes on the "cxf:cxfEndpoint" itself and everything else I could think of from the various error messages along the way. Although this works, it creates a lot of clutter.

      Thanks!