• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1677
  • Last Modified:

How do I consume an AXIS2 Web Service in C#

One of our departments created an AXIS2 Web Service in JAVA so we can retrieve data for our IVR's.  Unfortunately the current systems we have do not consume web services, so I'm required to develop some middleware that consumes the web service and then the IVR communicates with my middleware to get the data it needs.   I was able to add the web service as a reference to the application, but when I build, I get this error:

Error      7      Schema item 'complexType' named 'SchemaType' from namespace 'http://xmlbeans.apache.org/xsd'.       App_WebReferences/DolEx/      

I am not sure how to proceed and time is critical on getting this web service running.  

I'm running Visual Studio 2008 SP1, using C# and I added the web reference by right-clicking in the solution explorer and clicking "Add Web Reference"
0
creatingworlds
Asked:
creatingworlds
  • 2
1 Solution
 
kittsCommented:
Use the command line tool "wsdl" to generate the proxy class. Then post the exact error here. If you can send me the wsdl file I can take a look at it. I have faced the same issue and fixed it by modifying the wsdl. sometines, the wsdl generated by the AXIS is not compatible with the .Net wsdl generator.

Here is how to use the command line utility wsdl.exe
http://msdn.microsoft.com/en-us/library/7h3ystb6.aspx

Also please try the soapclient test tool to test the AXIS webservice.
http://www.soapclient.com/soaptest.html
0
 
creatingworldsAuthor Commented:
Thanks for your help.  The above information helped me understand what the problem was, unfortunately the web service we are using is 3rd party, and I have no control over any of the information on that particular server / service.  Thanks again!
0
 
kittsCommented:
I am just adding some more information here. Even if you dont have control over the AXIS web service/server, you could get the wsdl file by browsing their webservice in IE. Then save it to your local IIS root. Then use your local wsdl location to generate proxy class(using wsdl.exe). In this way you could modify the wsdl until all the errors are fixed and a proxy class is generated. Then only thing you need to do is to add the newly generated proxy class file in your project and update the "this.url" property inside the proxy class file to match the other AXIS webservice. Hope this helps.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now