17.1 A Little History
When the MIDP v1.0 specification was released in 2000, it was a good compromise between the small footprint required by small devices at that time and features necessary to support simple mobile applications. Since then, capabilities of mobile devices and sophistication levels of mobile clients have increased drastically. MIDP v1.0 is showing its limitations. One such limitation is the lack of support to access structured data. To address this problem, a major design goal for the MIDP v2.0 specification was to add a set of XML and Web Services XML. However, during the development of MIDP v2.0, the expert group could not agree on the exact format, features, and footprint of the XML API. Considering that a large portion of MIDP v2.0 devices will be used for gaming applications and may never consume Web Services, the MIDP v2.0 expert group decided that the XML API should be offered as a standard Optional Package for both CLDC-based and CDC-based profiles. The specification development is delegated to a new expert group in Java Specification Request 172 (JSR 172, "J2ME Web Services Specification").The JSR 172 expert group consists of 30 industry-leading corporations and individuals. It includes all the big handset manufacturers (e.g., Nokia, Motorola, Sony/Ericsson, LG, Siemens, Sharp, and RIM), system software vendors (e.g., Symbian, IBM, Borland, BEA, and Sun Microsystems) and several leading wireless carriers (e.g., NTT and Cingular). The specifications have been unanimously approved by the JCP J2ME executive committee. An implementation of the J2ME Web Services Optional Package is already available from IBM's Web Services Tool Kit for Mobile Devices. This toolkit integrates with the WebSphere Studio Device Developer IDE. Now, let's have a look at the APIs proposed by JSR 172. |
لطفا منتظر باشید ...
