DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17703>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17703 Java2WSDL creates .Net interop incompatible map type Summary: Java2WSDL creates .Net interop incompatible map type Product: Axis Version: 1.1RC1 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: WSDL processing AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The apachesoap:Map type generated by Java2WSDL produces a map type that WSDL.exe does not want to play well with. by defining a ComplexType for item as a child of Map for the items wsdl.exe complains with the error of "Error: Unable to import binding 'FooSoapBinding' from namespace 'htt p://test'. - Unable to import operation 'bar'. - Types must be declared at the top level in the schema." If the emitted xsd defined the Map as two types then WSDL.exe plays nice with the gerenated data.... <schema targetNamespace="http://xml.apache.org/xml-soap"; xmlns:apachesoap="http://xml.apache.org/xml-soap"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns="http://www.w3.org/2001/XMLSchema";> <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/> <complexType name="Item"> <all> <element name="key" type="xsd:anyType"/> <element name="value" type="xsd:anyType"/> </all> </complexType> <complexType name="Map"> <sequence> <element name="item" type="apachesoap:Item" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> </schema>
