'http://xml.apache.org/xml-soap:Element'?
I suspect not. Your DOM element should be defined a <xsd:anyType>, not as apachesoap:Element.
Of course, you should avoid passing undefined types if possible. If you know the schema of the element you'd like to exchange, then you should define it in your WSDL.
Anne
Hi Guys,
I am having a problem regaring interoperablility, when i try to build a
.NET proxy for my Axis web service it raises an error on Dom Element, i
have a doc/lit style web service that accepts Dom Element as a parameter
and returns Dom Element, but .NET generates an error when building
proxy, the error message is:d:\SpecSheetGenerator\WindowsApplication2\Web References\WebReference\Reference.map(1): Custom tool error: Unable to import WebService/Schema. Unable to import binding 'ProductDocumentServiceSoapBinding' from namespace 'http://192.168.30.134:8080/myService/services/MyService '. Unable to import operation 'myMethod'. The datatype 'http://xml.apache.org/xml-soap:Element ' is missing.
can any one help me to fix this issue?
Thanks in advance.
Regards,
Muhammad Iqbal
From: "Hansen, Geir" < [EMAIL PROTECTED]>
Reply-To: [email protected]
To: <[email protected]>
Subject: RE: problem in developing .NET proxy for Axis web services
Date: Tue, 22 Nov 2005 18:16:34 +0100
>I think that "generates an error" is not spesific enough to be able to
>help you.
>Can you describe the problem in a bit more detail?
>
>
>-----Original Message-----
>From: MUHAMMAD IQBAL [mailto: [EMAIL PROTECTED]]
>Sent: 22. november 2005 17:28
>To: [email protected]
>Subject: problem in developing .NET proxy for Axis web services
>
>Hi Guys,
>
>I am having a problem regaring interoperablility, when i try to build a
>.NET proxy for my Axis web service it raises an error on Dom Element, i
>have a doc/lit style web service that accepts Dom Element as a parameter
>and returns Dom Element, but .NET generates an error when building
>proxy.
>
>can any one help me to fix this issue?
>
>Thanks in advance.
>
>Regards,
>
>Muhammad Iqbal
>
>
