DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8340>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8340 Empty value in WSDL soapAction attribute [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-04-21 14:59 ------- WSDL is not required to contain an SOAPAction. The SOAP client you are using is incorrectly depending on the SOAPAction to determine the operation name. AXIS COULD generate WSDL that puts the operation name into the SOAPAction, but this would lead to another problem. If we start with WSDL to create a service, then when that service exports a WSDL file (via ?WSDL), that WSDL should contain the same SOAPAction that the original WSDL file contained. We won't override it. This SOAPAction may be anything. It need not be the operation name. So even if we change OUR SOAPAction from "" to "<operationName>", it won't always be "<operationName>", so your client will be depending on something that is not guaranteed. I'm setting the resolution to INVALID. Reopen the bug if you disagree with my assertions.
