KSoap2 size

Hi

Just a reminder...
MIDP specs don't allow pakages greater than 30KB.
KSoap2 size is 57Kb...
I don't think it will work in MIDP Profile.

Thks
Kappy
----- Original Message -----
From: "Kappy" <[email protected]>
To: <[email protected]>
Sent: Thursday, May 08, 2003 11:25 PM
Subject: Ksoap: Re: kSOAP & IIS & .NET (once again)


> Hi
>
> Thaks for the Tip...
> kSOAP2, with small changes on the XMLPULL worked for me.
> Altrouhgt I've had ro recompile all the source code of xmlpull, kobjects,
> kxml2 and ksoap because it givies me an error in verification class and
> stackmap fault.
>
> Thanks a Lot.
> Kappy
>
>
> ----- Original Message -----
> From: "Stefan Haustein" <[email protected]>
> To: <[email protected]>
> Sent: Thursday, May 08, 2003 8:36 PM
> Subject: Re: Ksoap: kSOAP & IIS & .NET (once again)
>
>
> > Hi Kappy,
> >
> > kSoap should not "see" the HTTP header fields; the Java HTTP connection
> > provides access to header fields in special methods, but not via the
> > content stream.  To figure out if this is a client or server side
> > problem, I recommend to try the same sample in another MIDP emulation,
> > e.g. the WTK or the  ME4SE.
> >
> > Please note that kSOAP 1.x probably will still not be able to parse the
> > .NET response properly if the server is not configured for the SOAP
> > serialization (you may either change your server configuration or better
> > use kSOAP 2.x)
> >
> > Best,
> > Stefan
> >
> > >Hi.
> > >
> > >I've found a strange error:
> > >In the simplest .NET Framework exemple of a webservice (retrurning a
> "Hello
> > >World" string with no params), being comsumed by kSOAP 1.2 running with
> > >nokia 6310 SDK.
> > >The strange is that I've managed to do the correct calling, to the WS
but
> > >when it begins to parse the responce it throws an ParseException :
> > >unexpected: ParseEvent type=128 text='HTTP/1.1 200 OK Server:
> > >Microsoft-IIS/5.1 Date: Wed, 07 May 2003 19:30:00 GMT Cache-Control:
> > >private, max-age=0 Content-Type: text/xml; charset=utf-8
Content-Length:
> 371
> > >' @-1:-1
> > >
> > >It is normal that it try to parse the HTML headers?
> > >and what about that strange char in the end? "' @-1:-1"
> > >I've used a packed snifer and the server is returning the right thing:
> > >HTTP/1.1 200 OK
> > >Content-Type: text/xml; charset=utf-8
> > >Content-Length: 371
> > >
> > ><?xml version="1.0" encoding="utf-8"?>
> > ><soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > >xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > >xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
> > >  <soap:Body>
> > >    <HelloWorldResponse xmlns="http://desktop/WebService3/">
> > >      <HelloWorldResult>Hello World</HelloWorldResult>
> > >    </HelloWorldResponse>
> > >  </soap:Body>
> > ></soap:Envelope>
> > >
> > >Sorry my bad english...
> > >João Matos Silva
> > >Portugal
> > >
> > >
> > >
> > >_______________________________________________
> > >Ksoap mailing list
> > >[email protected]
> > >http://www.enhydra.org/mailman/listinfo.cgi/ksoap
> > >
> > >
> >
> >
> > _______________________________________________
> > Ksoap mailing list
> > [email protected]
> > http://www.enhydra.org/mailman/listinfo.cgi/ksoap
> >
> >
>
>
> _______________________________________________
> Ksoap mailing list
> [email protected]
> http://www.enhydra.org/mailman/listinfo.cgi/ksoap
>