About JCP
Get Involved
Community Resources
Community News
FAQ
Contact Us

|
 |
JSRs: Java Specification Requests
JSRs by Platform
Certain JSRs are part of one or more of the platforms: collections of standards that comprise the three Java editions: Standard, Enterprise and Micro. Many JSRs are not part of the platform, but rather augment that platform; those JSRs are not listed on this page. This page lists the JSRs that comprise the various versions of the three platform editions.
Java EE (54 JSRs) | Java SE (79 JSRs) | Java ME (85 JSRs)
Java ME
Java ME technology, Java Micro Edition, specifically addresses the vast consumer space, which covers the range of extremely tiny commodities such as smart cards or a pager all the way up to the set-top box, an appliance almost as powerful as a computer.
Description
The Real-Time Specification for Java extends the JavaTM platform to support both current practice and advanced real-time systems application programming.
Description
This specification will define a standard platform configuration of the JavaTM 2 platform, Micro Edition (J2METM) for small, resource-limited, connected devices.
Spec Lead
Antero Taivalsaari, Sun Microsystems, Inc.
Description
The Connected Device Configuration (CDC) provides the basis of the JavaTM 2 platform, Micro Edition for devices that have a sufficient 32-bit microprocessor and ample memory.
Spec Lead
Jon Courtney, Sun Microsystems, Inc.
Description
This specification will define a profile that will extend and enhance the "J2METM Connected, Limited Device Configuration" (JSR-000030), enabling application development for mobile information appliances and voice communication devices.
Description
The Foundation Profile is a set of APIs meant for applications running on small devices that have some type of network connection.
Spec Lead
Jon Courtney, Sun Microsystems, Inc.
Description
The Distributed Real-Time Specification for Java extends RMI in the Real-Time Specification for Java, to provide support for predictability of end-to-end timeliness of trans-node activities.
Reason
The Specification Lead has chosen to list this JSR as dormant while work on the Community Review draft continues.
Latest Stage
Expert Group Formation
Description
The J2METM Personal Profile provides the J2ME environment for those devices with a need for a high degree of Internet connectivity and web fidelity.
Spec Lead
Jon Courtney, Sun Microsystems, Inc.
Description
The J2METM RMI Optional Package (RMI OP) provides JavaTM platform
to Java platform remote method invocation for Java devices and
interoperates with J2SETM RMI.
Spec Lead
Mark Hodapp, Sun Microsystems, Inc.
Description
This specification will define the next major revision of the JavaTM 2 platform, Micro Edition.
Reason
Its original purpose to define the architecture for Java ME and additional processes for building blocks are not necessary. The Community Review draft contains useful working definitions of Configurations and Profiles and useful rules for subsetting and merging APIs.
Description
This JSR produces two separate optional packages for features commonly found on PDAs and other J2ME mobile devices: one for accessing PIM data and one for accessing file systems.
Spec Lead
Tom Chavez, PalmSource, Inc.
Ken Walker, IBM
Description
This specification provides a JavaTM API for communicating with devices
attached via the Universal Serial Bus (USB). It allows Java applications to discover, read, write, and manage USB devices.
Description
Bluetooth is an important emerging standard for wireless integration of small devices. The specification standardizes a set of Java APIs to allow Java-enabled devices to integrate into a Bluetooth environment.
Description
This JSR extends the work of the 1.0 JavaTM Speech API, specifying a cross-platform interface to support speech recognizers and synthesizers.
Spec Lead
Charles Hemphill, EverSpeech, Inc.
Description
This specification will define a profile that will extend and enhance the "J2METM Mobile Information Device Profile" (JSR-000037).
Spec Lead
Volker Bauche, Oracle
Description
This defines a set of optional APIs which provides standard access to wireless communication resources, designed to run on J2ME configurations and to enhance J2ME profiles with unique functionality.
Spec Lead
Marquart Franz, Siemens AG
Description
The J2METM Personal Basis Profile provides a J2ME application environment for network-connected devices supporting a basic level of graphical presentation.
Spec Lead
Jon Courtney, Sun Microsystems, Inc.
Description
Defines a Java 2 Micro Edition Profile for the purposes of game development targeting high-end consumer game devices and desktops.
Reason
The Spec Lead has chosen to withdraw this JSR. It was determined that the needs of games developers were best served by moving to a pure open source model for game client technologies. This changes in strategy will allow the broadest participation by the game development community, and will focus the energies of the community on timely solutions that address a rapidly changing technology landscape. The Spec Lead wishes to thank the Java Community and the Game Developers who supported and showed interest in this effort.
Spec Lead
Bartley Calder, Sun Microsystems, Inc.
Description
This specifies a small-footprint multimedia API for J2METM, allowing simple, easy access and control of basic audio and multimedia resources while also addressing scalability and support of more sophisticated features.
Description
Specifies standard APIs for performance metric instrumentation of Java programs.
Reason
Withdrawn at the request of the Specification Lead.
Description
This specification will define a revised version of the J2METM Connected, Limited Device Configuration (CLDC).
Description
JavaDesk provides a standard desktop API across platforms using an MVC model. Applications can control and
enhance the desktop using the JavaDesk API.
Reason
This JSR was not approved by the SE/EE Executive Committee in the JSR Approval Ballot.
Spec Lead
Rich Isaac, Bay Equities, Inc.
Description
SIMPLE Presence provides a standard portable and secure interface to manipulate presence information between a SIMPLE client (watcher) and a presence server (presence agent).
Spec Lead
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory
Description
SIMPLE Instant Messaging provides a standard portable and secure interface to exchange messages between SIMPLE clients. SIMPLE is an extension of SIP to support presence and instant messaging.
Spec Lead
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory
Description
The proposed specification will define a JDBC Optional Package for Java 2 Micro Edition (J2ME), Connected Device Configuration (CDC) Foundation
Profile.
Description
The purpose of this specification is to define an optional package that provides standard access from J2ME to web services.
Spec Lead
Jean-Yves Bitterlich, Oracle
Description
This specification will provide J2ME applications with APIs for security and trust services through the integration of a Security
Element.
Spec Lead
Saqib Ahmad, Oracle
Roman Zelov, Sun Microsystems, Inc.
Description
Defines an optional package that will facilitate the emergence of the market for the development of compelling games on mobile phones. The API shall work with MIDP1.0.
Reason
This JSR was not approved by the ME Executive Committee in the JSR Reconsideration Ballot.
Spec Lead
Thomas Landspurg, In-Fusio SA
Description
An Optional Package that enables developers to write mobile location-based applications for resource-limited devices. The
API works on the J2ME CLDC v1.1 and CDC configurations.
Spec Lead
Kimmo Loytana, North Sixty-One Ltd
Cheng Wang, Nokia Corporation
Description
SIP API for J2ME defines a multipurpose SIP API for J2ME clients. It enables SIP applications to be executed in memory limited terminals, especially targeting to mobile phones.
Spec Lead
Erkki Rysä, North Sixty-One Ltd
Cheng Wang, Nokia Corporation
Description
This proposed JSR will provide a scalable, small-footprint, interactive 3D API for use on mobile devices.
Spec Lead
Tomi Aarnio, Nokia Corporation
Erkki Rysä, North Sixty-One Ltd
Description
This JSR will provide an overall architectural description as well as an integrated TCK and RI to coordinate
selected JCP efforts for the wireless industry.
Description
Presence is a generic and protocol-agnostic API for Presence, providing a standard portable and secure interface to control, manage and manipulate Presence information between Presence clients and servers.
Spec Lead
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory
Description
A protocol-agnostic API for Instant Messaging, this provides a standard portable and secure interface to control, manage and manipulate instant messages between clients through the use of presence servers.
Spec Lead
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory
Description
This defines an optional code package that standardizes application event tracking on a mobile device and the submission of these event records to an event-tracking server via a standard protocol.
Spec Lead
Shai Gotlib, Amdocs Management Ltd.
Description
This JSR will define a J2ME profile targeting embedded networked devices that wish to support a Java runtime environment, but that do not have graphical display capabilities.
Spec Lead
Thomas Lampart, Cinterion Wireless Modules GmbH
Jari Lansio, Nokia Corporation
Description
This JSR will extend and enhance the "Wireless Messaging API" (JSR-000120)
Spec Lead
Marquart Franz, Siemens AG
Description
The Advanced Graphics and User Interface (AGUI) Optional Package will migrate the core APIs for advanced graphics and user interface facilities from the J2SE platform to the J2ME platform.
Spec Lead
Hakim Mendjeli, Vodafone Group Services Limited
Roger Riggs, Oracle
Description
Enabling J2METM applications to handle multi-media and web content can give developers and users a seamless and integrated user environment on mobile phones and wireless devices.
Description
Effort to define another layer of the J2ME Web Service stack, implementing the 'observable' behavior of a choreographed Web Service on the Device, relative to the message exchange requiring support.
Reason
This JSR was not approved by the ME Executive Committee in the JSR Approval Ballot.
Spec Lead
Ash Parikh, IOPSIS Software Inc.
Description
This JSR is to provide a standard set of APIs for J2ME Devices for representing and manipulating Collaboration Profile and Agreement information described by ebXML CPP/A (Collaboration Protocol Profile/Agreement) documents.
Reason
This JSR was not approved by the ME Executive Committee in the JSR Approval Ballot.
Spec Lead
Ash Parikh, IOPSIS Software Inc.
Description
This JSR will update the existing Personal Profile (JSR-62) specification to reflect the J2SETM 1.4 APIs).
Spec Lead
Jon Courtney, Sun Microsystems, Inc.
Roger Riggs, Oracle
Description
This JSR will update the existing Personal Basis Profile (JSR-129) specification to reflect the J2SETM 1.4 APIs.
Description
This JSR defines a revision to the J2ME CDC specification. This JSR provides updates (based on J2SE, v1.4) to the existing core, non-graphical Java APIs for small electronic devices.
Description
This JSR defines a revision to the J2ME Foundation Profile. This JSR provides updates (based on J2SE, v1.4) to the existing core, non-graphical Java APIs for small electronic devices.
Description
This specification will define an optional package API for rendering scalable 2D vector graphics, including image files in W3C Scalable Vector Graphics (SVG) format.
Spec Lead
Juha Eskelinen, Nokia Corporation
Kimmo Loytana, North Sixty-One Ltd
Description
This specification will define a profile that will extend and enhance the "J2METM Information Module Profile" (JSR-195).
Spec Lead
Thomas Lampart, Cinterion Wireless Modules GmbH
Description
Enabling application developers to initiate mobile payment transactions in J2METM applications.
Spec Lead
Jean-Yves Bitterlich, Oracle
Description
Enabling J2METM applications to access native data synchronization implementation
Reason
The Specification Lead chose to list this JSR as dormant in August 2011.
Description
Create a predictable management environment for mobile devices capable of installing, executing, profiling, updating, and removing JavaTM and associated native components in the J2METM Connected Device Configuration.
Spec Lead
Venkat Amirisetty, Motorola
Cheng Wang, Nokia Corporation
Description
This specification will define an optional package for advanced multimedia functionality which is targeted to run as an supplement in connection with MMAPI (JSR-135) in J2ME/CLDC environment.
Spec Lead
Erkki Rysä, North Sixty-One Ltd
Cheng Wang, Nokia Corporation
Description
This JSR defines an API that provides culturally correct data formatting, sorting of text strings and application resource processing for J2ME MIDlets running in MIDP over CLDC.
Spec Lead
Jere Kapyaho, Nokia Corporation
Erkki Rysä, North Sixty-One Ltd
Description
JavaTM bindings to the OpenGL ES (Embedded Subset) native 3D graphics library.
Description
The requested specification will define a J2ME profile based on the Connected Limited Device Configuration (CLDC) that is appropriate for use by small-footprint cable television set top boxes.
Spec Lead
Donald Bleyl, Cox Communications, Inc.
Jens Paetzold, Oracle
Description
Enabling J2METM applications to access device management implementations
Reason
The Specification Lead chose to list this JSR as dormant in August 2011.
Description
This JSR creates a mobile service architecture and platform definition for the high volume wireless handsets continuing the work started in JSR-185 and enhancing the definition with new technologies.
Spec Lead
Guenter Klas, Vodafone Group Services Limited
Erkki Rysa, Nokia Corporation
Description
This JSR defines the next generation of the Mobile Service Architecture and platform created in JSR 248.
Reason
The Specification Leads chose to list this JSR as dormant in August 2012.
Spec Lead
Adamu Haruna, Nokia Corporation
Guenter Klas, Vodafone Group Services Limited
Description
This JSR creates a mobile telephony API and platform definition which utilizes common telephony features and is small and simple to suite to high volume devices with limited resources.
Spec Lead
Jean-Yves Bitterlich, Oracle
Brian Deuser, Motorola
Description
The API provides general Sensor API that extends the usability and choice of sensors for J2ME applications. It defines generic sensor functionality optimized for the resource-constrained devices like mobile devices.
Spec Lead
Kimmo Loytana, North Sixty-One Ltd
Pia Niemela, Nokia Corporation
Description
This specification will define J2ME Optional Packages for contactless communication, one package for bi-directional communication and the other for accessing read-only information.
Spec Lead
Kimmo Loytana, North Sixty-One Ltd
Jaana Majakangas, Nokia Corporation
Description
The Mobile User Interface Customization API provides a way to query and modify the user interface customization properties of a mobile device or platform.
Spec Lead
Jere Kapyaho, Nokia Corporation
Erkki Rysä, North Sixty-One Ltd
Description
The purpose of this JSR is to define an API that enables communication between mobile devices in a peer-to-peer ad-hoc network environment.
Reason
The Specification Lead chose to list this JSR as dormant in August 2011.
Spec Lead
Volker Bauche, Oracle
Description
The purpose of this JSR is to define an API to access and manage the message boxes of the mobile device and their content.
Reason
The Specification Lead chose to list this JSR as dormant in May 2012.
Description
This JSR will specify the 3rd generation Mobile Information Device Profile, expanding upon the functionality in all areas as well as improving interoperability across devices.
Description
This specification will define an optional package in J2ME/MIDP/CLDC environment to provide functionality to handle broadcast content, e.g. to view digital television and to utilize its rich features and services.
Spec Lead
Kimmo Loytana, North Sixty-One Ltd
Antti Rantalahti, Nokia Corporation
Ivan Wong, Motorola
Description
RM API will provide a simple interface for resource reclamation, accounting, and monitoring in a Java ME platform that requires resource management for multiple applications.
Reason
The Executive Committee voted to list this JSR as dormant in May 2012.
Spec Lead
Ho An, Samsung Electronics Corporation
Hobum (Vincent) Kwon, Samsung Electronics Corporation
Description
A new high-level API for connection services via frameworks supporting identity based services, discovery, and authentication. The API supports Service Oriented Architectures (SOA) and other similar network service application models.
Spec Lead
Kimmo Loytana, North Sixty-One Ltd
Pia Niemela, Nokia Corporation
Jens Paetzold, Oracle
Description
This JSR provides a common general purpose XML API for the next generation of mobile devices.
Spec Lead
Jean-Yves Bitterlich, Oracle
Pia Niemela, Nokia Corporation
Description
This JSR provides a high-level API to access IP Multimedia Subsystem (IMS) services. This API hides IMS technology details and exposes service-level support to enable easy development of IMS applications.
Spec Lead
Piotr Kessler, Ericsson AB
Stefan Svenberg, Ericsson AB
Description
Fill some minor gaps in the RTSJ
Description
This specification will define an optional package for rendering enhanced 2D vector graphics and rich media content based on select features from SVG Mobile 1.2, with primary emphasis on MIDP.
Spec Lead
Juha Eskelinen, Nokia Corporation
Kimmo Loytana, North Sixty-One Ltd
Description
This specification will define a mechanism that enables a systems developer to include multiple Configurations and Profiles on a single device, using one set of developed components.
Reason
This JSR was not approved by the ME Executive Committee in the JSR Approval Ballot and JSR Reconsideration Ballot.
Spec Lead
Andre Kruetzfeldt, Aplix Corporation
Description
This JSR enables creation of Java ME applications which combine Web
UI markup technologies with Java code. The intent is to leverage
the W3C Compound Document Format (CDF) specification.
Reason
The Specification Lead chose to list this JSR as dormant in August 2012.
Spec Lead
Jean-Yves Bitterlich, Oracle
Description
This specification defines an optional package that enables the developers to use new enhanced location-based features on the JavaTM ME devices.
Spec Lead
Kimmo Loytana, North Sixty-One Ltd
Jaana Majakangas, Nokia Corporation
Description
This new revision of M3G (JSR-184) will expose the latest graphics hardware features on high-end devices, while improving performance and memory usage on the low end.
Reason
The Specification Leads chose to list this JSR as dormant in June 2013.
Spec Lead
Tomi Aarnio, Nokia Corporation
Erkki Rysä, North Sixty-One Ltd
Description
This JSR defines the API set for Telematics Service on mobile devices.
Spec Lead
Dave Kim, SK Telecom Co., Ltd.
Young Min Park, SK Telecom Co., Ltd.
Description
This specification will define an optional package for developing JavaTM ME applications which
utilize or interoperate with DRM agents that separately exist in devices.
Spec Lead
Jea Un Kim, LG Electronics Inc.
Dnyanesh R Pathak, LG Electronics Inc.
Description
This specification creates a J2METM capability, based on the Real-Time Specification for Java (JSR-1), containing minimal features necessary for safety critical systems capable of certification, e.g., DO-178B.
Spec Lead
C. Douglass Locke, The Open Group
Description
This JSR extends the interfaces defined in JSR253 (Mobile Telephony API) to cover additional use cases and features not covered in that JSR.
Reason
The Executive Committee voted to list this JSR as dormant in May 2012.
Latest Stage
Expert Group Formation
Description
This JSR provides API's for initiating and controlling data sessions in a mobile device and providing applications control over wireless network selection.
Reason
The Executive Committee voted to list this JSR as dormant in September 2012.
Description
This specification will define a high level, lightweight services and management framework API's that will provide JME based devices the ability to manage long running applications and services.
Reason
The Executive Committee voted to list this JSR as dormant in May 2012.
Latest Stage
Expert Group Formation
Description
This specification will define a high level, IMS Communications Enabler framework API that will provide Java ME based devices effortless access to a set of essential IMS Communication Enablers.
Spec Lead
Martin Gunnang, Ericsson AB
Niclas Palm, Ericsson AB
Description
This JSR will enable Java application to interact with dynamic content delivery (DCD) client implementation in user's device.
Reason
The Executive Committee voted to list this JSR as dormant in September 2012.
Spec Lead
Dave Kim, SK Telecom Co., Ltd.
Description
CLDC 8 will be an evolutionary update to CLDC 1.1.1 to bring the VM, Java Language, and libraries up to date with Java SE 8.
Spec Lead
Michael Lagally, Oracle
Roger Riggs, Oracle
Description
Update IMP(-NG) to align with state-of-the-art features and current embedded device market requirements.
Spec Lead
Volker Bauche, Oracle
Description
The maintenance of the Java TV specification.
Spec Lead
Michael Lagally, Oracle
Jens Paetzold, Oracle
|