Re: problem in developing .NET proxy for Axis web services
Anne, You are write, i did not define 'http://xml.apache.org/xml-soap:Element' in my WSDL but my .NET client contacts to Axis for WSDL and Axis generates WSDL automatically, i am not involved in generating that at all. do you have any suggestion, that how to change this entry or fix this issue? Regards, Muhammad Iqbal cell :0092-300-9377801 From: Anne Thomas Manes <[EMAIL PROTECTED]> Reply-To: axis-user@ws.apache.org To: axis-user@ws.apache.org Subject: Re: problem in developing .NET proxy for Axis web services Date: Sat, 26 Nov 2005 13:18:03 -0500 Do you have this type defined in your WSDL: 'http://xml.apache.org/xml-soap:Element'? I suspect not. Your DOM element should be defined a , 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 On 11/25/05, MUHAMMAD IQBAL <[EMAIL PROTECTED]> wrote: > > 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: ** > 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: axis-user@ws.apache.org > >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 > > > > > >
Re: problem in developing .NET proxy for Axis web services
Do you have this type defined in your WSDL: 'http://xml.apache.org/xml-soap:Element'? I suspect not. Your DOM element should be defined a , 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. AnneOn 11/25/05, MUHAMMAD IQBAL <[EMAIL PROTECTED]> wrote: 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, ihave a doc/lit style web service that accepts Dom Element as a parameter and returns Dom Element, but .NET generates an error when buildingproxy, 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: axis-user@ws.apache.orgTo: <axis-user@ws.apache.org>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: axis-user@ws.apache.org>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>>
Re: problem in developing .NET proxy for Axis web services
hi dear I also trying to interoperability but I don't any idea about that.(Java client to .net(C#) service and vice versa).If you acheive this any way please let me know how you acheive this.Becouse i am a newer to this field. thank you madushan thilina. It is better if you send that detai below mail: [EMAIL PROTECTED]MUHAMMAD IQBAL <[EMAIL PROTECTED]> wrote: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, ihave a doc/lit style web service that accepts Dom Element as a parameterand returns Dom Element, but .NET generates an error when buildingproxy, 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: axis-user@ws.apache.orgTo: Subject: RE: problem in developing .NET proxy for Axis web servicesDate: 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: axis-user@ws.apache.org>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>> Yahoo! Music Unlimited - Access over 1 million songs. Try it free. Yahoo! Music Unlimited - Access over 1 million songs. Try it free.
RE: problem in developing .NET proxy for Axis web services
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: axis-user@ws.apache.org 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
