SOAPAction HTTP header required.

[Ken Pelletier]

I have a service which I've moved from Apache SOAP to Axis and am now testing.

Apart from a couple of things, it's working quite well.

I have one instance where a particular client application can no longer make calls to the service now that it's been placed under Axis, but could when it was under Apache SOAP.

The client app, which is not under my control, does not send a SOAPAction HTTP header, so Axis always returns a 'no SOAPAction header!' fault to the client.

How can I get my service to consumer messages w/o SOAPAction HTTP headers under Axis?

- Ken