Is there any variation in the way domain names are represented in the WSDL's? I've found interoperability problems between Axis and .NET due to variations in the way domain names were spelled out. It's hard to tell when you are doing black box testing, but from what I've seen Axis treats a schema in MyDomain.com as being different from a schema in mydomain.com while .NET treats them as being synonymous. -- Andy
>>> [EMAIL PROTECTED] 12/21/04 04:09PM >>> Hello, We have an Axis based WebService Server with some of the consumers on the .net platform. The clients on the .net platform is having trouble with the wsdl that is generated by Axis, though other Axis based clients and some perl based clients are running fine. This Axis generated wsdl for our service has duplicate namespace declarations and the .net client is faling with the error, "A schema with the namespace 'http://x.y.com/a/b/c' has already been added." Top part of the wsdl : <?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions targetNamespace="http://x.y.com/a/b/c"; xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:apachesoap="http://xml.apache.org/xml-soap"; xmlns:impl="http://x.y.com/a/b/c"; xmlns:intf="http://x.y.com/a/b/c"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:tns1="http://x.y.com/a/b/c"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; Request for any pointers on this, We would like to know if anyone has faced this problem, and any solutions/workarounds that might be there. Thanks! Shain.
