IIRC, the SOAPAction header is deprecated. If you have freedom to change the WSDL contract, then your service would do better as rpc/literal than document/literal: this wraps x in the name of the operation and allows dispatching based only on the SOAP content, not on the transport details.
However, I wasn't aware that SOAPAction support was missing/broken in Axis. On Wed, 9 Nov 2005, Per Steffensen wrote: > Hi > > I have a document/literal Axis webservice (EJB provided). It contains to > operations "a" and "b" that take that same kind of parameter "x". I > generate client stubs to call the webservices though java client code. I > have looked at the request send over the wire (using af http sniffer), > when calling "a" and "b" respectivly. The only difference between the > two request is the SOAPAction header. It is "a" and "b" respectivly. But > it is the method "a" on the EJB that is called to in both cases. I have > operation-tags in server-config.wsdd for both operations, and I have put > soapAction attributes on them. Any idea why it does not work? Why is > method "b" on the EJB not called when I call method "b" on the generated > client stubs (and SOAPAction header is "b" in the request)? > > Kind regards, Steff > Guy Rixon [EMAIL PROTECTED] Institute of Astronomy Tel: +44-1223-337542 Madingley Road, Cambridge, UK, CB3 0HA Fax: +44-1223-337523
