I don't know of a way to avoid this, other than to change the Axis code to not throw an exception when the SOAPAction is empty. This might not be a bad idea as I believe the that the usage of the SOAPAction has not been formalized yet. On the client side (using the MS SOAP toolkit) I got around this by using the low-level MS SOAP api rather than the high-level api. The low-level api allos you to specify this (which btw can be set to anything, although convention seems to be "webServiceName#methodName").
Xander ----- Original Message ----- From: "Ken Pelletier" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 27, 2002 11:14 AM Subject: SOAPAction HTTP header required. > 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 > >
