With Java Axis as a web service provider, the client uses C #.
Calling everything goes well, it does not get the return value. The return value is a BOOL type, but it is always false. Use AXIS's TCPMON to monitor SOAP messages, and it is not unpleasant, and it is impossible to determine whether the client is problematic when parsing the SOAP response.
Later, I tried to monitor the SOAP message with the SOAP TRACE Utility inside MS SOAP SDK, I found that the SOAP message could not be displayed:
The xml page cannot be displaphi
Cannot View XML Input Using Style Sheet. Please Correct The Error and The Click The Refresh Button, or try again lat
Invalid at the top level of the document. Error Processing resource 'file: /// C: / Documents and settings / zzephyr / local settings / temp / mssoapt.0 / m69.xml'. Line 1, position 1
1A7
^
Use "View Source" to find out more "1A7":
1A7
Suspected is a problem with AXIS, which outputs a strange character. Later, it was discovered that not AXIS issues. That 1A7 is the length of the message, which is the representation of Chunk Encoding. It is TRACE UTILITY to explain CHUNK ENCODING correctly. Throwing Trace Utility regardless of the .NET client. The client's code is automatically generated according to the WSDL file. The original MS default SOAP response XML element is
Result, and AXIS default is
RESPONSE.
Change the responseElementName inside SOAPDocumentMethodAttribute
RESPONSE's format is ok.
I checked the W3C's norm, as if I didn't specify the naming specification for the elements. No one is right, wasted the time of developer! Thank USABCD (3 of the Communications on Highways on Highways) give me a useful information
