Hi there- By looking at http://servicemix.apache.org/servicemix-http-new-endpoints.html it looks like the servicemix-http soap-provider can have a setting for the soapAction. Applying that to a soap-provider endpoint results in failure in deployment of the SA using the component due to not supported attribute. This information at the link above seems incorrect compared with the http schema at http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/servicemix/servicemix-http/2008.01/servicemix-http-2008.01-schema.html#soap-provider .
In reason to get around it, I needed to edit the message headers manually in another Bean endpoint prior forwarding the massage to the soap-provider endpoint to change the soapAction to reflect the one expected by the remote soap-provider. Is this always going to be the case with this particular component usage, or there will be a solution for that anytime soon? Asen-
