It's a bad idea to use rpc/literal because quite a few major SOAP stacks (.NET, BEA, SAP, etc) don't support it.
What you should use is document/literal with the "wrapped" convention.
If you are generating the WSDL using java2wsdl, specify that you want
the "wrapped" style. If you are using the W
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
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
