Title: .NET has problems with Axis complex types?
Thanks!
 
Hmm, how "safe" is it in general to use the nightly build instead of alpha3. Or when will there be a new stable version?
 
Thomas
-----Original Message-----
From: Glen Daniels [mailto:[EMAIL PROTECTED]]
Sent: Mittwoch, 6. Februar 2002 17:14
To: '[EMAIL PROTECTED]'
Subject: RE: .NET has problems with Axis complex types?

If you try a recent nightly build, you should find that the Hashtable is correctly described in the generated WSDL.  This was fixed last weekend, I believe.
 
--Glen
-----Original Message-----
From: Thomas Börkel [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 06, 2002 10:54 AM
To: [EMAIL PROTECTED]
Subject: RE: .NET has problems with Axis complex types?

This is the complex type, that Axis defines for a return type of Hashtable. Isn't there something missing???
 
 <types>
  <schema targetNamespace="http://xml.apache.org/xml-soap" xmlns="http://www.w3.org/2001/XMLSchema">
   <complexType name="Map">
    <sequence/>
   </complexType>
   <element name="el0" nillable="true" type="tns4:Map"/>
  </schema>
 </types>
-----Original Message-----
From: Thomas Börkel
Sent: Mittwoch, 6. Februar 2002 15:12
To: Axis Mailinglist
Subject: .NET has problems with Axis complex types?

HI!

Using Axis alpha2 and .NET final.

If I have a method, which returns a Hashtable, then Axis defines this as a complex type=Map in the WSDL. If I consume then this WSDL in .NET, then it does not generate a Proxy for this service. While manipulating the "URL behavior" property from "static" to "dynamic" (what I usually always do), then finally .NET issues an error message like this:

The custom tool 'MSDiscoCodeGenerator' failed.  Unable to import binding 'AuftragSoapBinding' from namespace 'urn:p2sales.p2plus.apag.com'.


The service is called "Auftrag". I also tried a namespace like "http://p2sales.p2plus.apag.com".

Any ideas anyone? Without the mentioned method with the complex type, the same WSDL works in .NET.


Thanks!

Regards,
Thomas

Reply via email to