Hi,
This may be the interoperability issue.
Please make sure that "namespace" specified in WSDL for complex type is same
as that of generated in WSDD file for the specified complex type. i.e.
"targetNamespace" tag value in WSDL should be same as "typeMapping"
namespace value.
Amit
On 3/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
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.exetool
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
