01-15-2010 01:13 AM
I am very new to web services.
I developing an application for BB 4.5 version. I using a webservcies to get data from a asp.net server.
I converted the wsdl using WTK 2.1.
Now while trying to call a services I am getting "SAXParseException in the return SOAP message from the server." error message.
But I am not able to debug exactly where this error is.
I noticed one thing in the response that one of the element is empty and it is "<Reference />.
Can this be the reason of the error?
Thanks for your help in advance.
03-31-2010 09:34 AM
i am in the same boat as you.. have you been able to resolve your issue?
i have not been able to find any documentation on implementing jsr 172 on blackberry.. if anyone has located a tutorial, please post a link
RIM needs to get on this and provide support for bb developers
03-31-2010 10:10 AM
I don't have much experience with jsr 172, i'm afraid. I've been drowning in kSOAP2 lately, though...
That said, my assumption based on the message above is that your response may be malformed -- or at least not in the form you expect. You may want to get a sniffer such as TCPMon or EtherDetect to see exactly how the response is built.
Hope that helps,
03-31-2010 10:31 AM
hi dom, thanks for the reply
i've already implemented ksoap2, but am looking to migrate to jsr172.. with ksoap2 you must write your own xml parsing, which tends to be a lot slower than the optimised jsr 172
also, w/ ksoap2 i had to write my own connection classes, whereas w/ jsr172, i think it's not necessary
03-31-2010 10:35 AM
I didn't say that kSOAP2 was the "be all end all". Being completely new to web services, that's just the first thing I found, and it's what I learned on. I only discovered jsr 172 a few weeks ago, but I haven't needed to use it. As such, I'm afraid I can't really be of use in that regard.
09-28-2010 04:35 AM
I've the same problem, I get a SaxParseException in the return SOAP message from the server.
Can anybody help me, please???
Thanks for your help.
10-28-2010 07:37 AM
02-14-2012 12:08 AM
this problem is caused if the url is not properly formed with the ksoap stubs, like we need to modify the stubs according to bb device for eg. for wifi,bbsid , etc