I have a customer with a WSDL file and 2 levels of schema files (shema file 
1 refers to elements in schema file2) and they say the web service works 
with .net and java, however, it does not work with some other products.

Not working means the client fails to generate the correct SOAP message. 
The SOAP message is incorrect because some of the fields needed are not 
present.

I loaded the WSDL and schema files into the SOAP tool at soapclient.com and 
had it generate a SOAP request message.  The fields were missing from the 
SOAP body.

I searched google for "WSDL validator" and tried the files in the other 
validators.  In some of the validators, the fields showed up, in other 
validators, the field were not there but in every case, when I tried to 
assign a value to the fields, none of the tools would assign the values, the 
SOAP body elements were always empty.

Still curious as to what is going on, I downloaded XMLSpy (a nice $1000 tool 
but I used the free trial period) and loaded the files into it.  I generated 
a web service call and the fields showed up in the body of the SOAP message. 
However, when I tried to assign a value to those fields, XMLSpy said they 
are not accessible because of the namespace.

I noticed XMLSpy assigned a namespace called 'a' to those fields.  So, I 
think there are definitely namespace issues going on.

My question is, why would these files work with some products like .net but 
other products, including XMLSpy, fail?

I understand that different companies will implement differing amounts of 
the w3c recommendations but if the three fields were not accessible due to a 
namespace issue, I would expect .net to to report the same thing.  In fact, 
I think the soapclient.com tool is written using MS libraries.

Any insights appreciated.

Thanks.

--g