Is it just the Authorization header or any type of header you add? What you have looks good, so I'm not sure why it's not working. You can actually add the same header in your composer (or service logic) by setting a context property with an EndpointLabel.HTTP label (scope = OUT in 0.8, MESSAGE in 1.0). You can see from the code that it's actually doing the exact same thing you are though:
i'm observing that the headers i explicitly add are lost somewhere downstream of the call to _dispatcher.invoke(soapMessage) on line 253 of the SOAP OutboundHandler.
this occurs even when setting properties with an EndpointLabel as you've described.
i'm wondering what the recommended approach is to invoke from Switchyard a remote SOAP service that is secured using basic authentication ?
This feature has been added recently and will be out in 1.0.0 release. https://issues.jboss.org/browse/SWITCHYARD-1567
is the correct approach to create a custom SOAP message composer similar to this example (in particular the decompose() function) ?
the custom SOAP message composer approach i've attempted (as per my example) using latest SY master branch seems to drop the 'Authorization' headers
By default, only the headers that are mapped in the config will be passed through. To enable this header, change the SwitchYard config as below for the reference binding.
<soap:binding.soap> <soap:contextMapper includes="Authorization" includeNamespaces=".*" soapHeadersType="VALUE"/> ... </soap:binding.soap>
I can't use 1.0, need to stay on 0.8 until newest version supports community release of JBoss AS. In my case both service URL and wsdl URL are protected, they require basic authentication. Can I use this service with Switchyard 0.8? If yes., how exactly do I polug in credentials (same userid/password for accessing wsdl and performing all invocations)?