h2. Foreword As mentioned in part 1 (Developing an android client for a business application – part 1), I won’t be able to present fully functioning code, only some snippet, and I’ll try to focus on the interface between ABAP and Android/Java.Since it’s coming out pretty long, I had to put the Android specific stuff in part 3 (Developing an android client for a business application – part 3) . h2. Web service On the SAP side, I wrote a simple web service.This consists in a class implementing interface IF_HTTP_EXTENSION and an ICF entry:
The link between the two is in the details of the web service:
The link between the two is in the details of the web service:
Nice blog, thanks for sharing. I used the same approach a year ago but didn’t find enough time to post my findings on SDN.
You could also use the JSON format to reduce the amount of data sent to the device. You can use ZJSON (http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=163840922) to generate the JSON data and Jackson (http://jackson.codehaus.org/) to process it on the Android device.
Regards,
Pierre
I did think about JSON for that very reason, but I didn’t know ZJSON.Better, I vaguely remembered something about it but I didn’t even search for it: I wanted to keep my options open for shipping this stuff to my customers, and that means everything has to be in our /BTI/ namespace.
Good point anyway, I would still advocate JSON for this kind of application if data size is a major concern.XML still looks better for documenting it to a third party though.
I hope you’re right: don’t know much about it but I always like to have options.
http://www.odata.org/
http://code.google.com/p/odata4j/
But I’ll try to get a better look when I have time or need to publish services to third parties.