Find JSRs
Submit this Search

Ad Banner

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 205: Wireless Messaging API 2.0

Stage Access Start Finish
Final Release Download page 04 Jun, 2004  
Final Approval Ballot View results 06 Apr, 2004 19 Apr, 2004
Proposed Final Draft Download page 05 Nov, 2003  
Public Review Download page 03 Jun, 2003 03 Jul, 2003
Community Draft Ballot View results 29 Apr, 2003 05 May, 2003
Community Review Login page 02 Apr, 2003 05 May, 2003
Expert Group Formation   10 Feb, 2003 14 Mar, 2003
JSR Review Ballot View results 28 Jan, 2003 10 Feb, 2003
Status: Final
JCP version in use: 2.6
Java Specification Participation Agreement version in use: 2.0

This JSR will extend and enhance the "Wireless Messaging API" (JSR-000120)

Please direct comments on this JSR to the Spec Lead(s)

Specification Leads
  Marquart Franz Siemens AG
Expert Group
  Aplix Corporation Cellon France SAS Cingular Wireless
  Esmertec AG iaSolution Inc. Intel Corp.
  IOPSIS Software Inc. Kada Systems Macromedia, Inc.
  Motorola Nokia Corporation Sharp Corporation
  Siemens AG Sony Ericsson Mobile Communications AB Sun Microsystems, Inc.
  Symbian Ltd Telefonica Of Spain Vodafone Group Services Limited

Updates to the Original JSR

The following updates have been made to the original request.

Maintenance Lead: Marquart Franz

E-Mail Address:

Telephone Number: +49 89 636 48767

Fax Number: +49 89 636 45450

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Member: Siemens AG

Name of Contact Person: Jan Eichholz

E-Mail Address:

Telephone Number: +49 89 722 21405

Fax Number: +49 89 722 53164

NOTE that this information has been updated from this original request.

Specification Lead: Jan Eichholz

E-Mail Address:

Telephone Number: +49 89 722 21405

Fax Number: +49 89 722 53164

Initial Expert Group Membership:

Siemens AG

Supporting this JSR:


Section 2: Request

2.1 Please describe the proposed Specification:

This specifaction will define an interface for sending and receiving MMS. It's not the scope of this JSR to offer interfaces for visualization!

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

Like JSR 120 the new WMA 2.0 should be applicable to all MIDP versions.

2.3 What need of the Java community will be addressed by the proposed specification?

Possibility for Java applications to compose, send and receive MMS messages. It's not the scope of this JSR to offer interfaces for visualization!

2.4 Why isn't this need met by existing specifications?

JSR 120 is offering a message framework. At the moment it offers only the possibilities to deal with Broadcasted and Short Messages.

2.5 Please give a short description of the underlying technology or technologies:

With the WMA 2.0 it will be possible for Java applications to compose and send messages, which can contain text, images and sound. This technology allows a richer possibility for messaging on mobile devices. For the realisation the framework of JSR 120 will be used.

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)


2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

MMS (see 3.1)

2.8 Are there any security issues that cannot be addressed by the current security model?

No. The platform that this API is implemented on needs to have a security framework that can be used to enforce the appropriate policy. Defining the security framework is out of the scope for this JSR. For example, the MIDP 2.0 security framework can be used.

2.9 Are there any internationalization or localization issues?


2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?


2.11 Please describe the anticipated schedule for the development of this specification.

Expert Group formation: Feb 2003
Community Draft: Mar 2003
Public Draft: May 2003
Final Draft: August 2003
RI & TCK: September 2003

2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.

Initial face to face meeting. Conference Calls and EMail. Additional meetings if necessary.

2.13 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.

Stand-Alone, it should at least be combinable with MIDP 1.0.

2.14 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).


2.15 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

For early information and subject to change, as defined in the JCP process.
- Siemens will license to all interested parties.
- It is intended to charge a single one-time fee for RI/TCK and annual maintenance fee. A per-unit royalty fee will be charged for the RI.

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

JSR 120:
JSR 118:
MMS-API: 3GPP TS 23.140 V4.4.0

3.2 Explanation of how these items might be used as a starting point for the work.

This JSR should use as a basis the framework offered by JSR 120.
The necessary integration with the security framework of JSR 118 will be specified.
For WMA 1.0 the MIDP 2.0 spec was not ready so that JSR 120 could define the WMA 1.0 - MIDP 2.0 relation. WMA 1.0 only specifies in the security section "... applications MUST be granted a permission to perform the requested operation. The mechanisms for granting permission are implementation dependent ..."
WMA 2.0 will specify the relation regarding the existing MIDP 2.0 security model by defining the integration. WMA 2.0 will NOT define an own security model.