|
Actually I just checked and the WSDL from the server specified that the SOAPAction should be “” (See below), so I think this might be an Axis 2 bug that it’s still sending the SOAPAction as “urn:Getinfo”. Anyone know a way around this?
From the WSDL… <wsdl:operation name="Getinfo"> <soap:operation soapAction="" style="document" /> … </wsdl:operation>
-----Original Message-----
I’m writing a client and I have an issue where the release 1.0 version of Axis 2 works and the latest build does not. I’m using code generated from WSDL2JAVA. The problem appears to lie on the server (not Axis). For some reason if the HTTP has anything but a blank SOAPAction header (i.e. SOAPAction: “”) it fails with a fault of “unknown operation”. In the 1.0 version of Axis 2 it sends a blank SOAPAction. In the latest build of Axis 2 it always seems to send the operation name as the soap action. For example I have an operation named Getinfo. In the stub, the method Getinfo specifically sets the action to “” as follows… _operationClient.getOptions().setAction(""); Yet the header still contains “SOAPAction: urn:Getinfo”. I understand the server should probably accept that header, but since I have no control over the server, is there anyway to stop the action from being set? Thanks! Todd This message, including any attachments, is the property of Sears Holdings Corporation and/or one of its subsidiaries. It is confidential and may contain proprietary or legally privileged information. If you are not the intended recipient, please delete it without reading the contents. Thank you. This message, including any attachments, is the property of Sears Holdings Corporation and/or one of its subsidiaries. It is confidential and may contain proprietary or legally privileged information. If you are not the intended recipient, please delete it without reading the contents. Thank you. |
Title: SOAPAction
- SOAPAction Doolittle, Todd
- RE: SOAPAction Doolittle, Todd
