Printed: May 5, 2024
From: http://jcp.org/en/jsr/detail?id=172
|
Specification Leads | |||
Jean-Yves Bitterlich | Oracle | ||
Expert Group | |||
Aplix Corporation : Michael Leone |
Barreto, Charlton : Charlton Barreto |
BEA Systems : Jim D'Ambrosia |
|
Cingular Wireless : Roger N. Mahler |
Cisco Systems : Krishna Sankar |
Fujitsu Limited : Satoshi Kikuchi |
|
Hewlett-Packard : Sandeep Chatterjee |
Hutchison 3G UK Limited : Jamie Hayes |
IBM : Joe Rusnak |
|
Insignia Solutions : Priyen Doshi |
LG Telecom : JH C |
Motorola : Paul Kline |
|
Netdecisions Holdings United : Steve Jones |
Nokia Corporation : James Reilly |
NTT Software Corporation : Takayuki Tachikawa |
|
Oracle : Jean-Yves Bitterlich |
Oracle : Jimmy Shi |
Ortiz, C. Enrique : C. Enrique Ortiz |
|
Panasonic Information and Network Technologies Laboratory : Alan Kaplan |
Research In Motion, LTD (RIM) : Russell Owen |
SAP SE : Stefan Schwing |
|
Sharp Corporation : Hideyuki Otokawa |
Siemens AG : Calinel Pasteanu |
Siemens AG : Marc Schlichte |
|
Smart Fusion : Jean Finka |
Sony Ericsson Mobile Communications AB : Par-Anders Aronsson |
Sony Ericsson Mobile Communications AB : Peter Stark |
|
Sun Microsystems, Inc. : Jean-Yves Bitterlich |
Sun Microsystems, Inc. : Cliff Draper |
Sun Microsystems, Inc. : Roger Riggs |
|
Symbian Ltd : Simon Lewis |
Wilson, John : John Wilson |
Yospace Holdings Ltd. : Tim Russell |
|
Contributors | |||
NOTICE: Please be aware the CDC 1.0 specification initially related to this JSR has been replace (superseded) with the newer CDC 1.1 specification. CDC 1.0 will no longer be supported after 18-Aug-2009. This JSR and other optional technologies based on the CDC 1.0 standards are fully compatible with the CDC 1.1 standards. All development and certification efforts should be updated to use the current, supported technology.
The following information has been updated from the original proposal:
2011.09.09: The Maintenance Lead changed the JCP version of this JSR from JCP 2.1 to 2.7.
2008.12.12:
The Maintenance Lead was changed to:
Specification Lead: Jean-Yves Bitterlich
E-Mail Address: jean-yves.bitterlich
Telephone Number: +49 89 46008 1097
Fax Number: -
Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification
Submitting Member: Sun Microsystems, Inc.
Name of Contact Person: Danny Coward
E-Mail Address: danny.coward@sun.com
Telephone Number: +1 408 276 7049
Fax Number: +1 408 276 7191
Specification Lead: Jon Ellis, Mark Young
E-Mail Address: jon.ellis@sun.com, mark.young@sun.com
Telephone Number: +1 408 276 7633
Fax Number: +1 408 276 7191
Initial Expert Group Membership:
TBD
Section 2: Request
There is great interest and activity in the Java community in the use of web services standards and infrastructures to provide the programming model for the next generation of enterprise services. There is considerable interest in the developer community in extending enterprise services out to J2ME clients.
This JSR is designed to provide an infrastructure as two optional packages for J2ME to:-
The specification is targeted for the J2ME platform including the CLDC- and CDC-based profiles.
Since J2ME contains only low level programming and communication APIs to support web services, the barrier is high for the developer to take advantage of the new web service technologies. Currently the enterprise developer of J2ME clients to enterprise services is offered a number of non-standard and proprietary approaches for communicating with web services.
Although JSR 63 (JAXP) and JSR 101 (JAX-RPC) define Java APIs and conventions for XML processing and XML based RPC targeted at the J2SE and J2EE platforms, they will not provide such facilities for the J2ME developer. This is because the desgn center for these specifications does not take into account the different constraints, such as footprint, on J2ME devices.
See 2.1
Where this optional package uses APIs that are subsets of established packages, the original package name will be used. Should any original APIs be created by this JSR, they would be in javax.microedition.
No. The goal of this work is to provide optional packages suitable for J2ME devices.
An implementation should take advantage of the security model of the underlying environment.
No
No. We aim that this work will leverage the protocols, data formats, and definition languages belonging to network interoperability standards groups such as W3C or OASIS. We aim that this specification will subset the APIs and conventions defined by JAXP and JAXRPC where possible, and so will be complementary with the existing and ongoing work in the Java Community on XML processing (JAXP) and XML based RPC messaging.
Community Review: Dec 2002
Final Release: Summer 2003
We anticipate the expert group will follow the model of the JSR118 expert group and others, using in the main email communications with occasional telephone and possibly face to face meetings, which will be teleconferenced.
Section 3: Contributions
J2ME Platform specification
http://jcp.org/jsr/detail/68.jsp
J2ME Connected, Limited Device Configuration (CLDC) Version 1.0, May 2000
http://jcp.org/aboutJava/communityprocess/final/jsr030/index.html
http://java.sun.com/products/cldc
J2ME Mobile Information Device Profile (MIDP)
http://jcp.org/aboutJava/communityprocess/final/jsr037/index.html (Version 1.0)
http://jcp.org/jsr/detail/118.jsp (MIDP_NG)
http://java.sun.com/products/midp
J2ME Connected Device Configuration
http://jcp.org/jsr/detail/36.jsp
JavaTM API for XML Processing 1.1
http://jcp.org/jsr/detail/63.jsp
JavaTM APIs for XML based RPC
http://jcp.org/jsr/detail/101.jsp
W3C Web Services Activity web site. This includes a variety of information on the
W3C's work on XML Protocol, which includes support for RPC using XML.
http://www.w3.org/2002/ws
WSDL specification 1.0
http://www.w3.org/TR/wsdl
SOAP Protocol Specification v 1.1
http://www.w3.org/TR/SOAP/
WAP Binary XML Content Format
http://www.w3.org/TR/wbxml/
This optional package should work with CLDC- and CDC-based profiles, in particular MIDP, should subset the APIs defined in JSRs 063 and 101, and should support standard industry protocols for connecting with web services.