How to set these variables for ksoap2?

by amishera » Sat, 20 Sep 2008 01:26:49 GMT

Sponsored Links
I have this web service using apache cxf:


with method


Now I am using ksoap2 on client side in android. But I am not sure how
I should set the following variables:

    private static final String SOAP_ACTION = "...";
    private static final String METHOD_NAME = "...";
    private static final String NAMESPACE = "...";
    private static final String URL = "...";

as used in the code:

SoapObject request = new SoapObject(NAMESPACE, METHOD_NAME);
SoapSerializationEnvelope envelope = new
HttpTransportSE androidHttpTransport = new HttpTransportSE
(URL);, envelope);

Please help.

Thanks in advance.


Other Threads

1. JDOM in Android 2.1 or earlier

Hi all,

I was trying to use JDOM to parse a response from my REST web service,
when it threw a StringIndexOutOfBoundsException. I dug into the code
and I found that Exception is thrown in a substring method when the
JDOM is trying to recover something like a property name. I did a
little search in the Internet about it and I found it's a known bug:

So, has anybody been able to parse a document using JDOM in Android



2. getPreviewSize() bad result on Froyo emulator

Hello all,

I was trying to use some of the new camera methods included in Froyo,
i.e. setPreviewCallbackWithBuffer() & addCallbackBuffer(). In the
documentation it's said you need first to create a buffer of
appropriated size and use the addCallbackBuffer() method. The buffer
size must be width * height * bits_per_pixel or otherwise you'll never
receive a preview frame. To know the image size, you can ask to the
camera about it's configuration. When I'm trying to configurate the
camera I use Camera.getParameters().getPreviewSize() the emulator says
the size is 320*240, but with that size it didn't work on emulator. I
used the old setPreviewCallback() and, in the onPreviewFrame(), I
asked the size again. That time the size was 480*320. Then I hard-
coded that values in the first code and everything worked.
Now I'm afraid not only the emulator would have that behaviour.
Unfortunately I don't have any real device with Froyo and I can't try
it. So, anyone have tried that methods in real devices? btw, are they
really increasing the poor performance and frame rate?



3. media player application which shall dump Frame Rate and CPU Utilization

4. Socket connection using native socket() functions

5. SurfaceFlinger uses too much cpu

6. User Mode Device Drivers

7. USB Android gadget