Just a little remark. It should not be a problem, but maybe in the future cause for undetectable bugs:
The Extensible Markup Language (XML) 1.0 (Second Edition)
W3C Recommendation 6 October 2000 states in its section 3 "Logical Structures" (http://www.w3.org/TR/REC-xml#sec-logical-struct) the following:
This specification does not constrain the semantics, use, or (beyond syntax) names of the element types and attributes, except that names beginning with a match to (('X'|'x')('M'|'m')('L'|'l')) are reserved for standardization in this or future versions of this specification.
So maybe one should not use element-tags starting with "xml".
Good luck with your project, Christoph
Bobak, Greg P. wrote:
The nice thing about typing out a question is that I often answer it myself. The problem below is caused because the AXIS example was placing a namespace in the xml element that the .NET client was not:
<ns1:xml></ns1:xml>
vs.
<xml></xml>
G.
Greg Bobak Senior Programmer Analyst
Cole National
-----Original Message----- From: Bobak, Greg P. [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 09, 2003 11:08 AM To: Axis User Group Subject: .NET and Axis Namespace Incompatability
Hi,
We are working on creating an Axis client for a .NET web service. Our Axis client, created primarily with WSDL2java, creates the following SOAP body:
<soapenv:Body>
<ns1:process soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:ns1="CreditCardAuth">
<ns1:xml xsi:type="xsd:string">
BLAH
</ns1:xml> </ns1:process>
</soapenv:Body>
While our original .NET client creates the following body:
<soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> <tns:process> <xml xsi:type="xsd:string"> BLAH </xml> </tns:process> </soap:Body>
Where TNS is defined in the SOAP envelope like this:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:tns="CreditCardAuth" xmlns:types="CreditCardAuth/encodedTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
Note that the URI for ns1 and tns are the same "CreditCardAuth."
The .NET server reading the content of our process tags as empty. Is this because the xml element is not defined in the same namespace for each process above?
Thanks, Greg
Greg Bobak Senior Programmer Analyst
Cole National
http://www.thingsremembered.com
Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it.
Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it.
