If you are using the Web Services Resource Transfer specification you'll need to specify the specific namespace declaration http://schemas.xmlsoap.org/ws/2006/08/resourceTransfer/wsrt.xsd
If you're using the Wireless Sensor Network System then you will need to locate the xsd (or write one yourself) Of course your best bet is to find the person that created the WSDL and ask him for the specific locations of the XSD's Heres a PhD that started on that road last year http://mailman.doc.ic.ac.uk/pipermail/ukubinet-announce/2006-July/000235.html then again if you have the wsdl you can always grep for the string which follows 'xlmns:wsns' This WSNS is being called in almost every application I've seen Keep me apprised, Martin-- --------------------------------------------------------------------------- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------------- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. ----- Original Message ----- From: [EMAIL PROTECTED] To: [email protected] Sent: Wednesday, March 14, 2007 6:09 PM Subject: Axis2: Interop with .NET Hi.. We're trying to write a .NET client for our Axis2 Web Service. We have Java clients that work just fine using our WSDL, but the .NET wsdl.exe tool seems to choke on certain elements in our WSDL. Case in point: 1. The element name below has a whitespace in it. This is no problem for Axis1 or Axis2 WSDL2JAVA - but for .NET, I have to replace the white space with an underscore. <element name="ConnectionFailureFault"> <complexType> <sequence> <element name="Connection Failure" type="xsd:string"/> </sequence> </complexType> </element> I need to change the name as below: <element name="Connection_Failure" type="xsd:string"/> 2. Having trouble with namespaces too. <xsd:complexType name="SecurityType"> <xsd:sequence> <xsd:element name="UsernameToken" type="wsns:UsernameTokenType"/> </xsd:sequence> <xsd:anyAttribute namespace="##other" processContents="lax"/> </xsd:complexType> will only work with the WSDL.exe tool if the "wsns" is stripped from the type. My question to the group is: - Has anyone encountered this before using .NET wsdl.exe? - Is it possible we're not adhering to the rules of creating truly interoperable design contracts, even though AXIS2 WSDL2JAVA let our WSDL fly? Thanks \Sarwar
