Question on web service mobile client app for Android using ksoap2.

by Anjana » Fri, 23 Apr 2010 12:38:33 GMT


Sponsored Links
 Hi

I am creating web service clients in mobile devices (Android) through
the use of ksoap2 libraries.

 http://developer.ebay.com/DevZone/finding/Concepts/MakingACall.html 
states:
For the Finding API, no URL parameters or HTTP headers, including X-
EBAY-SOA-SECURITY-APPNAME can be specified in the SOAP header.

If they cannot be specified in SOAP header, how else can it done
(preferably using ksoap2 library). I tried appending parameters to the
URL, then calling AndroidHttpTransport androidHttpTransport = new
AndroidHttpTransport(URL); (everything else prior to the call is done,
sorry for not posting the code) but this yields soap fault.

Any thoughts/ suggestions? Thanks.
Anjana.

--



Other Threads

1. Including pre-compiled 3rd party jar files to android application & building it with source code

What do you mean by "build the application with android
source code"?  Are you building the entire platform or just your
application? And what problem do you encounter?





--~--~---------~--~----~------------~-------~--~----~

2. Market upgrade requires same certificate

Although I am using the same certificate and keystore, I am not able
to upload an upgrade of my application to the Android Market.  The key
is the same but may not appear to be since I changed platforms from PC
to Mac.  It is also possible that this is my mistake rather than a
bug.  Although the keystore is obviously named and the password is
correct, I might have created and used some other key...  It has been
months since I uploaded the last version of the app.  Is there
anything I can do to override the certificate errors I am hitting when
I use the 'upload upgrade' link?

The error is "The apk must be signed with at least one certificate in
common with the previous version."
To try and get around this, I unpublished, put in the updated apk, got
the same error, still no go. I unpublished and pushed out a refactored
apk.  No go.
I finally refactored to change the package name which allows me to
upload the upgrade as a new application. Of course, the old app is
still in place and I can't migrate existing users to give them the
upgrade.  Can I solve this problem?  If not, the Market is going to be
a mess of many versions of the same applications. (it already is
messed up this way, no? :)

Of course I like the added security of encryption and certificates so
that nobody can hack my app and upload malicious code under my name.
Today the protection is hampering my efforts, today it is inflexible.
Can I get a one time work-around for the certificate requirement so
that an upgrade will be published without the same certificate?  Any
feedback will be appreciated.

Regards,
Beth

--~--~---------~--~----~------------~-------~--~----~

3. Help - how to launch google chat intent

4. arm-eabi-4.4.0 toolchain source code

5. Can Android Framework API support multiple cameras?

6. Emulator is stalled when requestLocationUpdates API is used.

7. custom StateListDrawable