>Java heads have a tendency to "usurp" the word standard to mean "standard in the java environment", using it for conventions like sessionID managment in doc headers AFAIK not covered by WS semantics. And you are often better off just reimplementing before you get in to discussions [at least when the other side is gov. employed <vbg>]
Just to be sure, here is what I have in the upper part of the WSDL. Basically, I have adjusted it to avoid reflecting the client content:
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="CustomClientNamespace"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
targetNamespace="CustomClientNamespace"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="CustomClientNamespace">
<s:element name="ClientMethod">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Username" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Password" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Document" type="tns:CustomClientStructure" />
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="CustomClientStructure">
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="CustomClientSubStructureName" type="tns:CustomClientSubStructure" />
</s:sequence>
</s:complexType>
<s:complexType name="CustomClientSubStructure">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="MyField" type="s:string" />
</s:sequence>
</s:complexType>
</s:schema>Do you see a way for me to access this Web Service in .NET?
