Hello All, I have a wsdl document, which I got from one of my co-workers. He coded a MS Web Service which I want to connect too, but I am getting the following error.
I am guessing that this is because of there is a error in the WSDL document, specially at the beginning of the document. The WSDL document is kindda big so I will just give the starting part of the wsdl document.
I will appreciate any suggestions. Thanks for your help. -Amish
Did you leave out a few steps? It looks like you are trying to use the WSDL document directly with the SOAP server. WSDL gives enough information to create a SOAP client, but it is up to you to create the client. You might look into the GLUE SOAP application environment - http://www.themindelectric.com/ or Sun's XML Pack for utilities that can automatically read a WSDL and create a Java client. Bill
Hi William, Actually I am using WSAD( WebSphere Application Developer) IBM's IDE to actually create a Client with the information contained in the WSDL. The thing I do not understand is why am I getting the following error when I try to connect to the web service through my client
Are you saying that the client code got created and compiled without an error? If so than the WSDL is probably a valid file and you need to look at the client source code or the actual data transmitted by the client to see what is wrong with the namespace at line 4, position 36. I wrote a utility for trapping SOAP HTTP messages between client and server. You can download it from the page at: http://www.lanw.com/books/javasoap/ Bill
Actually WSAD contains a utility within it for monitoring the SOAP requests. I would suggest that you take a look at the help files provided with WSAD and then try using that utility to see what SOAP you are sending and compare it to what he is expecting. Kyle
Hi, Looks like the problem is because you are connecting to a M$ SOAP service. Following is an excerpt from http://xml.apache.org/soap/faq/ Does Apache SOAP work with Microsoft SOAP? Yes, but you need to install a patch to the MS SOAP package. One of the well-known interoperability problems between Apache 2.0 and MS Soap is that MS clients do not send type information with each parameter, and the Apache soap server will reject such requests. Hope that helps, Raj
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop