100 likes | 233 Views
Presentation 11: SOAP on small devices. Outline. Which small devices? What are the limitations and what kind of support do they offer for SOAP SDK’s available. Which small devices?. Embedded computers Windows CE Embedded LINUX and others PDA’s Pocket PC’s Windows CE, eC++, eVB
E N D
Outline • Which small devices? • What are the limitations and what kind of support do they offer for SOAP • SDK’s available
Which small devices? • Embedded computers • Windows CE • Embedded LINUX and others • PDA’s • Pocket PC’s • Windows CE, eC++, eVB • .NET Compact Framework & Pocket PC API • Palm • Running J2ME/J2SE or native Palm (C++) • Mobile phones • Native (Symbian C++, Personal Java) • J2ME CLDC MIDP • Smartphone API & .NET CF (Orange SPV, Motorola)
Problems with small computers • Limited memory and processing power • Limited storage facilities (no hard drive) • Limited bandwidth (for mobile phones using GSM/GPRS) • Not possible with full .NET Framework or J2SE JDK, big XML parser API’s – big footprints • SOAP and XML is bandwidth + processor demanding! • CONCLUSION: • SOAP CLIENT ONLY – NOT SERVER • Lightweight parser capabilities – not all features • Consider using alternatives
Pocket PC and Smartphone • Windows CE based operating systems does not have built in SOAP facilities • But it is possible with eMbedded Visual Tools • http://www.microsoft.com/downloads/details.aspx?FamilyID=f663bf48-31ee-4cbe-aac5-0affd5fb27dd&DisplayLang=en • Using Microsofts SOAP implementation for Windows CE • http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnppc2k2/html/ppc_reservices.asp • Or using Simon Fells PocketSOAP COM component – which even Microsoft has welcomed • http://www.pocketsoap.com/pocketsoap/ • .NET Compact Framework • SOAP is integrated in the .NET framework. No need to use eMbedded Visual Tools • But ONLY managed code works
J2ME CLDC & Mobile Phones • 2006: Apx. 70% of all new mobile phones support the Java 2 Mobile Edition SDK (Gartner Group) • No JVM –> KVM • -> cannot use AXIS and others • Build-in support for SOAP via JSR-172 (optional) • Including stub generation tools • Must check for support • http://www-128.ibm.com/developerworks/wireless/library/wi-jsr/ • Two alternatives • kSOAP: http://ksoap.org (footprint: 42K) • WingFoot: http://www.wingfoot.com/ (footprint: 35K) • No stub generation
JSR-172 • JSR 172 Web Services APIs (WSA) follow these core Web services specifications: • Simple Object Access Protocol (SOAP) 1.1 • Web Services Definition Language (WSDL) 1.1 • XML 1.0 • XML Schema • Note that JSR 172 does not support the Universal Description, Discovery, and Integration
Deployment Proxy Generation Request / Response
Developing for J2ME • Take a look at http://www.javasoft.com/J2ME • CLCD, MIDP • Development tools • Eclipse, NetBeans, JBuilder, JDeveloper, IntelliJ • NetBeans and JBuilder comes complete with J2ME JDK, Screen designer, Emulator, as well as JAD deployment utility
ANSI C SOAP Support • gSOAP (www.gsoap.org) supports ANSI C • Many platforms including Symbian • Stub generation + Web server • Borland C++ Builder development tool supports Symbian development and gSOAP