J2ME and SOAP

Thread view:

Altman - 03 May 2005 16:52 GMT

I am using netbeans to consume a web service written in VB.net. I am
having a problem getting this to work. I first tried doing this with
JSR 172 but got the error "Missing SOAP Body or Envelope." I did a
search on that and found that other people had this problem with no
idea how to fix it.
http://forums.java.sun.com/thread.jspa?threadID=520204&tstart=240 I
then tried using ksoap2. I downloaded the zip file and renamed it to a
jar file. I added the jar file to the library and the intellisense
shows that it is there but if I try to use any of the classes it says
that the class is missing or invalid. What am I doing wrong? how can
I get web services to work with J2ME?

Reply to this Message

Altman - 03 May 2005 22:09 GMT

Alright I got a little further with the kSoap (I think) but now it is
saying "Cannot find class java/io/FileReader" How can I get this class
available?

Reply to this Message

Altman - 04 May 2005 17:50 GMT

OK it was a mess to figure out, but I just took out driver.class in the
kObjects jar file I was then able to get it to work.

Reply to this Message

Darryl Pierce - 08 May 2005 13:06 GMT

> Alright I got a little further with the kSoap (I think) but now it is
> saying "Cannot find class java/io/FileReader" How can I get this class
> available?

You can't. java.io.FileReader is not a part of the MIDP and you cannot
(both legally and also be prevented by the MIDP implementation) add it
to your project. kSOAP shouldn't be using FileReader anyway, since it's
designed for the MIDP. Is the include in your code or the kSOAP code?

Signature

Darryl L. Pierce <mcpierce@gmail.com>
Visit my homepage: http://mcpierce.multiply.com
"By doubting we come to inquiry, through inquiry truth." - Peter Abelard

Reply to this Message

Altman - 09 May 2005 16:15 GMT

The Driver.class that was in the kObjects jar file was trying to access
the filereader class. The kObject.jar is needed for ksoap to work. I
don't know why the driver.class is included in it, or what it does but
after I removed this class from the jar file it compiled just fine. I
just hope the Driver.class isn't needed for anything. Also in reading
up on it, filereader is available in CDC but not CLDC. And of course I
am using CLDC.

Reply to this Message

Darryl Pierce - 10 May 2005 12:39 GMT

> The Driver.class that was in the kObjects jar file was trying to access
> the filereader class. The kObject.jar is needed for ksoap to work. I
[quoted text clipped - 3 lines]
> up on it, filereader is available in CDC but not CLDC. And of course I
> am using CLDC.

Trying putting the source code for kSOAP into your project, rather than
the JAR files, and compiling them along with your application. That way,
you'll get only those classes that are directly needed and can avoid
this kind of problem in future.

Signature

Darryl L. Pierce <mcpierce@gmail.com>
Visit my homepage: http://mcpierce.multiply.com
"By doubting we come to inquiry, through inquiry truth." - Peter Abelard

Reply to this Message

Altman - 10 May 2005 14:32 GMT

I did, the kSoap project you can put the code directly into your
project. But they rely on 2 jar libraries, kXml and kObjects. These 2
libraries are only available in jar files. The kObjects jar file had a
class in it that tried to use filereader which I took out of the jar
file.

Reply to this Message

J2ME and SOAP

Free Magazines