About JCP
Get Involved
Community Resources
Community News
FAQ
Contact Us
|
|
| 1 |
|
Real-time Specification for Java |
|
The Real-Time Specification for Java extends the JavaTM platform to support both current practice and advanced real-time systems application programming. |
|
Final
|
|
|
|
James Hunt, aicas GmbH |
 |
| 2 |
|
Boundary-Scan API |
|
This API targeted the JavaCardTM platform so as to allow it to be usable on all available JavaTM virtual machines from the very smallest to the most sophisticated. |
|
Withdrawn
|
|
Withdrawn at the request of the submitter. |
|
| Withdrawn |
|
Effective: 1999-01-09 |
|
|
|
Neil Jacobson, Xilinx |
|
Harold Ogle, Oracle |
|
| 3 |
|
JavaTM Management Extensions (JMXTM) Specification |
|
The JMXTM specification will provide a management architecture, APIs and services for building Web-based, distributed, dynamic and modular solutions to manage Java enabled resources. |
|
Withdrawn
|
|
Withdrawn following Maintenance Review 6. |
|
| Withdrawn |
|
Effective: 2014-03-05 |
|
|
|
Staffan Larsen, Oracle |
|
Hinkmond Wong, Oracle |
|
| 4 |
|
ECperf Benchmark Specification |
|
ECperf is an EJBTM performance workload that is real-world, scalable and captures the essence of why component models exist. |
|
Maintenance
|
|
| Maintenance Draft Review 2 |
Download page |
Start: 2002-03-19 |
End: 2002-04-22 |
|
|
Shanti Subramanyam, Sun Microsystems, Inc. |
|
| 5 |
|
XML Parsing Specification |
|
The JavaTM API for XML Parsing (JAXP) allows developers to easily use XML Parsers in their applications via the industry standard SAX and DOM APIs. |
|
Final
|
|
|
|
Rajiv Mordani, Oracle |
|
| 7 |
|
Industrial Automation Extension |
|
The Industrial Automation specification will result in an industry standard for industrial automation that is based on the JavaTM and JiniTM technologies. |
|
Withdrawn
|
|
Withdrawn with the consent of the Spec Lead. Difficulties in forming an expert group and reaching consensus toward a draft spec hampered the JSR's abilities in successfully navigating the community process. |
|
| Withdrawn |
|
Effective: 2004-10-11 |
|
|
|
Bruce Khavar, Cyberonix |
|
Tamsin Vantress, Cyberonix |
|
| 8 |
|
Open Services Gateway Specification |
|
This JSR was going to develop the Open Services Gateway (OSG) Specification and describe an extensible Service Gateway. |
|
Withdrawn
|
|
Withdrawn because work moved to Open Services Gateway consortium (www.osgi.org) where the specification will be completed. |
|
| Withdrawn |
|
Effective: 1999-05-10 |
|
|
|
Robert Mines, Sun Microsystems, Inc. |
|
| 9 |
|
Federated Management Architecture Specification |
|
The Federated Management Architecture (FMA) specifies a storage management platform that will allow vendors to construct storage management applications from standard and custom components. |
|
Maintenance
|
|
| Maintenance Draft Review |
Download page |
Start: 2000-08-18 |
End: 2000-09-18 |
|
|
William Connor, Phd., Sun Microsystems, Inc. |
|
| 11 |
|
JAINTM TCAP Specification |
|
JAINTM TCAP JSR is a proposed Java specification for the TCAP layer of the Signaling System 7 (SS7) stack. |
|
Final
|
|
|
|
Phelim O'Doherty, Sun Microsystems, Inc. |
|
| 12 |
|
JavaTM Data Objects (JDO) Specification |
|
The JDO specification provides for interface-based definitions of data stores and transactions; and selection and transformation of persistent storage data into native JavaTM programming language objects. |
|
Maintenance
|
|
| Maintenance Draft Review 2 |
Download page |
Start: 2004-10-25 |
End: 2004-12-06 |
|
|
Craig Russell, Sun Microsystems, Inc. |
|
| 13 |
|
Decimal Arithmetic Enhancement |
|
This primarily adds floating point arithmetic to the BigDecimal class, allowing the use of decimal numbers for general-purpose arithmetic without the problems resulting from conversions to and from another type. |
|
Final
|
|
|
|
Joe Darcy, Oracle |
|
| 15 |
|
Image I/O Framework Specification |
|
Image I/O supports image reader and writer plug-ins for sampled image formats. The API provides for exposure and preservation of metadata as well as pixel data. |
|
Final
|
|
|
|
Phil Race, Sun Microsystems, Inc. |
|
| 16 |
|
J2EETM Connector Architecture |
|
The J2EETM Connector architecture defines a standard architecture for integrating JavaTM applications with existing back-end Enterprise Information systems. |
|
Final
|
|
|
|
Binod PG, Sun Microsystems, Inc. |
|
| 17 |
|
JAINTM ISUP Specification |
|
Requirements for a Standard Java API for ISDN User Part (ISUP), an SS7 protocol. |
|
Withdrawn
|
|
The Spec Lead of this JSR approached other members of the Expert Group to see if they might be interested in taking on the role of Spec Lead, but there has been no interest. This is due to the fact that industry focus has evolved/changed, and as such the original scope of the JSR is not as important to the industry as originally scoped. The Spec Lead has since left the JCP and the Expert Group has been disbanded. |
|
| Withdrawn |
|
Effective: 2003-02-05 |
|
|
|
Vijaya Venkatachalam, Ulticom |
|
| 18 |
|
JAINTM OAM API Specification |
|
JAINTM Operations, Administration, and Maintenance (OAM) defines a standard API for provisioning and managing protocol interfaces in the Telecommunications and Internet Industry. |
|
Final
|
|
|
|
Doug Tait, Sun Microsystems, Inc. |
|
| 19 |
|
Enterprise JavaBeansTM 2.0 |
|
The Enterprise JavaBeansTM 2.0 specification extends the architecture with integration with JMS, improved support for entity bean persistence,
a portable query language for finder methods, and support for server interoperability. |
|
Maintenance
|
|
| Maintenance Draft Review |
Download page |
Start: 2002-02-20 |
End: 2002-03-25 |
|
 |
Linda Demichiel, Oracle |
|
| 20 |
|
Orthogonal Persistence for the JavaTM Platform |
|
Orthogonal persistence for the JavaTM platform (OPJ) would have provided persistence for the full computational model specified by the JavaTM Language Specification (JLS). |
|
Rejected
|
|
This work duplicates functionality to be provided by JSR-000012 Java Data Objects Specification. Work on Orthogonal Persistence continued at SunLabs. |
|
| Rejected |
|
Effective: 1999-08-11 |
|
|
|
Mick Jordan, Oracle |
|
| 21 |
|
JAINTM JCC Specification |
|
JSR 21 focuses on the JAINTM Java Call Control (JCC) Specification. Any references seen below that refer to the JAIN Coordination and Transactions (JCAT) are addressed in JSR 122. |
|
Final
|
|
|
|
Christer Boberg, Ericsson AB |
|
| 22 |
|
JAINTM SLEE API Specification |
|
Descriptions of all interfaces, classes, exceptions and requirements to develop portable telecommunication services and application frameworks so that services once developed will run on any JAINTM SLEE-compliant execution environment. |
|
Final
|
|
|
|
David Ferry, Open Cloud Limited |
|
| 23 |
|
JAINTM MGCP API Specification |
|
This work will specify the JAINTM API through which access to protocol stacks that support the Media Gateway Control Protocol (RFC 2705) may be achieved. |
|
Final
|
|
|
|
Christer Boberg, Ericsson AB |
|
| 24 |
|
JAINTM SPA TSM, SD and SAM 1.0 API |
|
This allows software developers to rapidly develop external Service Provider-type applications to securely access, discover and agree other APIs, which use abstract primitives that hide the heterogeneity of underlying networks. |
|
Final
|
|
|
|
Anders Lundqvist, Incomit AB |
|
| 26 |
|
UML/EJB Mapping Specification |
|
This document describes a standard mapping between the Enterprise JavaBeansTM architecture and the Unified Modeling Language. |
|
Withdrawn
|
|
Withdrawn due to lack of interest after the original Spec Lead company was acquired. New Spec Lead company has failed to find a Spec Lead who wants to drive JSR-26 to completion. Expert Group was informed of intent to withdraw JSR-26 and it supported that action. |
|
| Withdrawn |
|
Effective: 2004-03-29 |
|
|
|
Andy Dean, IBM |
|
| 27 |
|
JavaTM Cryptography Extension 1.3 |
|
This Specification would have enhanced the JavaTM Cryptography Extension 1.2 and made it exportable. |
|
Withdrawn
|
|
Withdrawn before work began because the proposal describes a cryptographic system and/or a cryptographic framework whose implementation would be subject to U.S. Export Licensing requirements. |
|
| Withdrawn |
|
Effective: 1999-11-05 |
|
|
|
Sharon Liu, Sun Microsystems, Inc. |
|
Jan Luehe, Sun Microsystems, Inc. |
|
| 28 |
|
Java SASL Specification |
|
This specification defines a SASL client and server API in the JavaTM programming language. |
|
Final
|
|
|
|
Rosanna Lee, Sun Microsystems, Inc. |
|
| 29 |
|
JAINTM MAP Specification |
|
The JAINTM MAP API Specification includes functionality for messaging and location service. The API may be implemented on different protocols, e.g. ETSI MAP and ANSI 41. |
|
Withdrawn
|
|
Withdrawn due to Spec Lead's move to another company and the lack of interest from the rest of the Expert Group in driving the spec to Final Release. At the time it was withdrawn, there had been no activity in the JSR since September 2001. |
|
| Withdrawn |
|
Effective: 2003-05-30 |
|
|
|
S?ren Torstensson, Ericsson Inc. |
|
| 30 |
|
J2METM Connected, Limited Device Configuration |
|
This specification will define a standard platform configuration of the JavaTM 2 platform, Micro Edition (J2METM) for small, resource-limited, connected devices. |
|
Final
|
|
|
|
Antero Taivalsaari, Sun Microsystems, Inc. |
|
| 31 |
|
XML Data Binding Specification |
|
A facility for compiling an XML schema into one or more JavaTM classes which can parse, generate, and validate documents that follow the schema. |
|
Final
|
|
|
|
Joe Fialli, Oracle |
|
Sekhar Vajjhala, Sun Microsystems, Inc. |
|
| 32 |
|
JAINTM SIP API Specification |
|
The JAINTM SIP API specification provides a standard portable interface to share information between SIP Clients and SIP Servers, providing call control elements enabling converged-network applications. |
|
Maintenance
|
|
|
|
Phelim O'Doherty, Oracle |
|
Mudumbai Ranganathan, NIST |
|
| 33 |
|
InfoBus 2.0 Specification |
|
The InfoBus 2.0 Specification and release would have added features to the existing InfoBus 1.2 Specification that capitalize on new features found in the J2SETM Platform. |
|
Withdrawn
|
|
Withdrawn at the request of the submitter. InfoBus 2.0 is no longer under development in the Java Community Process. Please direct comments or questions about InfoBus to infobus-comments@java.sun.com. For information on InfoBus 1.2, see http://java.sun.com/beans/infobus. |
|
| Withdrawn |
|
Effective: 1999-11-08 |
|
|
|
Mark Colan, Lotus Development Corporation |
|
| 34 |
|
JavaTM Advanced Imaging API 1.1 |
|
Revision of the JavaTM Advanced Imaging API specification to version 1.1. Java Advanced Imaging supports sophisticated image processing in Java 2. |
|
Final
|
|
|
|
John Zimmerman, Sun Microsystems, Inc. |
|
| 35 |
|
JAINTM INAP API Specification |
|
This JSR is to develop the JAINTM (Java APIs for Integrated Networks) INAP (Intelligent Network Application Protocol) specification for Intelligent Network Applications in the Telecommunications Industry. |
|
Final
|
|
|
|
Shankar Allimatti, Mahindra British Telecom Ltd. |
|
| 36 |
|
Connected Device Configuration |
|
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. |
|
Maintenance
|
|
|
|
Jon Courtney, Sun Microsystems, Inc. |
|
| 37 |
|
Mobile Information Device Profile for the J2METM Platform |
|
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. |
|
Final
|
|
|
|
Brian Deuser, Motorola |
|
| 38 |
|
Application Installation API Specification |
|
This proposal is to develop a set of Java APIs that will enable cross-platform installation and de-installation of JavaTM applications as well as platform-specific applications. |
|
Maintenance
|
|
| Maintenance Draft Review |
Download page |
Start: 2003-01-15 |
End: 2003-02-18 |
|
|
Paul Lovvik, Sun Microsystems, Inc. |
|
| 39 |
|
JavaTM Servlet and JSP Performance Benchmark |
|
The specification will provide a comprehensive benchmark suite for JavaTM Servlets and JSPTM pages that exercises the key areas that impact performance of these in real life applications. |
|
Withdrawn
|
|
Withdrawn at the request of the submitter. |
|
| Withdrawn |
|
Effective: 2001-10-02 |
|
|
|
Ruslan Belkin, America Online (AOL) |
|
| 41 |
|
A Simple Assertion Facility |
|
A new keyword allowing programmers to include assertions describing intended program behavior, which can be checked as programs execute to detect bugs. |
|
Final
|
|
|
|
Joshua Bloch, Sun Microsystems, Inc. |
|
| 42 |
|
Travel Industry Reservation Booking Foundation API Specification |
|
This intended to ease the building of applications for reservation booking in the travel industry that would cross all aspects of travel (air, car, hotel, cruise, and other travel activities). |
|
Withdrawn
|
|
Withdrawn at the request of the submitter. Community support was not sufficient to form an expert group. |
|
| Withdrawn |
|
Effective: 2000-06-13 |
|
|
|
Sherry Shavor, IBM |
|
| 43 |
|
JTAPI 1.4 Specification |
|
JTAPI 1.4 extends and enhances the current Java Telephony specification. |
|
Final
|
|
|
|
Jeff Peck, Enterprise Computer Telephony Forum (ECTF) |
|
Richard J. Pennenga, Enterprise Computer Telephony Forum (ECTF) |
|
| 44 |
|
Braille API Specification |
|
This API for Braille lines would have eased use of these devices and allowed faster introduction of new Braille lines in the JavaTM market by writing a driver for Braille. |
|
Withdrawn
|
|
Withdrawn at the request of the submitter. Community support was not sufficient to support an Expert Group. |
|
| Withdrawn |
|
Effective: 2000-11-21 |
|
|
|
Ramon Cabello, O.N.C.E. |
|
| 45 |
|
Debugging Support for Other Languages |
|
This specification establishes standardized tools for correlating JavaTM virtual machine byte code to source code of languages other than the JavaTM programming language. |
|
Final
|
|
|
|
Robert Field, Oracle |
|
| 46 |
|
Foundation Profile |
|
The Foundation Profile is a set of APIs meant for applications running on small devices that have some type of network connection. |
|
Maintenance
|
|
|
|
Jon Courtney, Sun Microsystems, Inc. |
|
| 48 |
|
WBEM Services Specification |
|
JavaTM WBEM Services is a set of APIs and reference implementation for WBEM. WBEM is an initiative from the DMTF that unifies systems management and instrumentation. |
|
Final
|
|
|
|
Carl Chan, WBEM Solutions, Inc |
|
Jim Davis, WBEM Solutions, Inc |
|
| 49 |
|
Web Based Industrial Monitoring Framework |
|
This JSR is to develop a web based monitoring and data acquisition framework for a industrial automation application. The APIs provides cross vendor inter-bean communication means. |
|
Withdrawn
|
|
Withdrawn as Spec Lead left the JCP and no other Expert Group member was willing to take over as Spec Lead. |
|
| Withdrawn |
|
Effective: 2010-02-18 |
|
|
|
Hiroaki Hashimukai, Yamatake Corporation |
|
| 50 |
|
Distributed Real-Time Specification |
|
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. |
|
Dormant
|
|
The Specification Lead has chosen to list this JSR as dormant while work on the Community Review draft continues. |
|
| Expert Group Formation |
|
Start: 2000-04-12 |
End: 2000-08-14 |
|
|
James Hunt, aicas GmbH |
|
| 51 |
|
New I/O APIs for the JavaTM Platform |
|
APIs for scalable I/O, fast buffered binary and character I/O, regular expressions, charset conversion, and an improved filesystem interface. |
|
Final
|
|
|
|
Mark Reinhold, Sun Microsystems, Inc. |
|
| 54 |
|
JDBCTM 3.0 Specification |
|
The proposed specification will update the JDBCTM specification to reflect changes in the SQL specification and JavaTM platform. |
|
Final
|
|
|
|
Lance Andersen, Oracle |
|
| 55 |
|
Certification Path API |
|
The Certification Path API provides a set of provider-based APIs for creating, building, and verifying certification paths (also known as "certificate chains"). |
|
Final
|
|
|
|
Sean Mullan, Sun Microsystems, Inc. |
|
| 60 |
|
Building Automation Java API |
|
The goal is to develop a set of Java APIs for programmable controllers in the building automation industry. |
|
Withdrawn
|
|
This JSR was originally proposed a long time ago, but failed to attract a critical mass for an expert group. After a few conference calls, the effort was abandoned. |
|
| Withdrawn |
|
Effective: 2016-04-05 |
|
|
|
Brian Frank, Tridium, Inc |
|
| 61 |
|
Phonelets API Specification |
|
Phonelets provide developers with a simple API to package, deploy and run Computer Telephony Integration (CTI) applications in a resource and security controlled environment. |
|
Withdrawn
|
|
Withdrawn at the request of the Spec Lead after 4 years with no Expert Group. |
|
| Withdrawn |
|
Effective: 2004-04-09 |
|
|
|
Marc Petit-Huguenin, 8x8 |
|
| 62 |
|
Personal Profile Specification |
|
The J2METM Personal Profile provides the J2ME environment for those devices with a need for a high degree of Internet connectivity and web fidelity. |
|
Maintenance
|
|
|
|
Jon Courtney, Sun Microsystems, Inc. |
|
| 64 |
|
Financial Services Party Component |
|
This JSR is a proposal to define an Enterprise Java BeanTM (EJBTM) component interface for party information as required by the financial services domain. |
|
Withdrawn
|
|
Withdrawn at the request of the submitter. XML party components for this functionality are being developed under the Customer Profile Exchange (CPex). |
|
| Withdrawn |
|
Effective: 2000-08-29 |
|
|
|
William Senn, IBM |
|
| 65 |
|
Concise Object-Array Literals |
|
A minor extension to the JavaTM programming language that will support a concise notation for automatically-boxing object-array literals. |
|
Withdrawn
|
|
Withdrawn at the request of the Spec Lead with the agreement of the Expert Group. The community requirements targeted in this JSR are now being addressed as part of autoboxing in JSR 201. |
|
| Withdrawn |
|
Effective: 2003-07-25 |
|
|
|
Gilad Bracha, Sun Microsystems, Inc. |
|
| 67 |
|
JavaTM APIs for XML Messaging 1.0 |
|
JAXM provides an API for packaging and transporting business transactions using on-the-wire protocols being defined by ebXML.org, Oasis, W3C and IETF. |
|
Maintenance
|
|
|
|
Lukas Jungmann, Oracle |
|
| 68 |
|
J2METM Platform Specification |
|
This specification will define the next major revision of the JavaTM 2 platform, Micro Edition. |
|
Withdrawn
|
|
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. |
|
| Withdrawn |
|
Effective: 2011-03-22 |
|
|
|
Roger Riggs, Oracle |
|
| 69 |
|
Java OLAP Interface (JOLAP) |
|
JOLAP is a pure Java API for the J2EETM environment that supports the creation and maintenance of OLAP data and metadata, in a vendor-independent manner. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. |
|
| Withdrawn |
|
Effective: 2012-04-16 |
|
|
|
John D. Poole, Hyperion Solutions Corporation |
|
| 70 |
|
IIOP Protocol Adapter for JMXTM Specification |
|
This specification will establish an IIOP based adapter for the JMXTM specification to allow CORBA clients access JMX agents. |
|
Withdrawn
|
|
Withdrawn following re-prioritization within the company, IONA could no longer commit the resources necessary to complete the specification and build an RI and TCK. In addition, IONA no longer sees a sufficient customer demand for access to JMX MBeans using CORBA clients, so IONA formed the opinion that the specification did not address a common need in the marketplace and therefore was unnecessary. |
|
| Withdrawn |
|
Effective: 2003-10-23 |
|
|
|
Damian McGrath, Progress Software |
|
| 71 |
|
JMX-TMN Specification |
|
JMX-TMN Specification is part of the second phase of the JavaTM Management Extensions (JMXTM) umbrella initiative. It specifies the interoperability between the Telecommunication Management Network (TMN) standards and JMX. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. |
|
| Withdrawn |
|
Effective: 2001-06-18 |
|
|
|
Aline Ellul, Evidian |
|
| 72 |
|
JavaTM GSS API |
|
This defines a Generic Security Services API (GSS-API) in Java, to provide a layer of abstraction over security mechanisms that perform authentication, message integrity protection, and message privacy protection. |
|
Final
|
|
|
|
Seema Malkani, Sun Microsystems, Inc. |
|
| 73 |
|
Data Mining API |
|
This JSR addresses the need for a data mining API aligned with existing, evolving data mining standards efforts. |
|
Maintenance
|
|
|
|
Mark F. Hornick, Oracle |
|
| 74 |
|
Public Key Cryptography Standards (PKCS) 1.0 |
|
This JSR is to define a standard set of APIs for a subset of the Public Key Cryptography Standards (PKCS#1, #5, #7, #8, #9, #10 and #12). |
|
Withdrawn
|
|
Withdrawn as the main goals of this JSR have been achieved and delivered through J2SE and other JCP specifications. |
|
| Withdrawn |
|
Effective: 2003-01-14 |
|
|
|
Seema Malkani, Sun Microsystems, Inc. |
|
| 75 |
|
PDA Optional Packages for the J2METM Platform |
|
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. |
|
Final
|
|
|
|
Tom Chavez, PalmSource, Inc. |
|
Ken Walker, IBM |
|
| 76 |
|
RMI Security for J2SETM |
|
Define a high-level API for network security in JavaTM 2 Standard Edition RMI, covering basic security mechanisms: authentication (including delegation), confidentiality, and integrity. |
|
Rejected
|
|
This JSR was not approved by the SE/EE Executive Committee in Draft Approval/Reconsideration Ballots. |
|
| Rejected |
|
Effective: 2001-02-21 |
|
|
|
Bob Scheifler, Sun Microsystems, Inc. |
|
| 77 |
|
J2EETM Management |
|
The JavaTM 2 Platform, Enterprise Edition Management Specification will provide server vendors and tool vendors with a standard model for managing the J2EE Platform. |
|
Maintenance
|
|
|
|
Hans Hrasna, Oracle |
|
| 78 |
|
RMI Custom Remote References |
|
Provide a general framework in JavaTM 2 Standard Edition RMI for customizing remote invocation behavior. |
|
Rejected
|
|
This JSR was not approved by the SE/EE Executive Committee in Draft Approval/Reconsideration Ballots. |
|
| Rejected |
|
Effective: 2001-02-21 |
|
|
|
Ann Wollrath, Sun Microsystems, Inc. |
|
| 79 |
|
JAINTM MEGACO API Specification |
|
This work will specify the JAINTM API through which access to protocol stacks that support the MEGACO/H.248 protocol may be achieved. |
|
Final
|
|
|
|
Vikas Bajaj, Hughes Software Systems |
|
| 80 |
|
JavaTM USB API |
|
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. |
|
Final
|
|
|
|
Boyd Dimmock, IBM |
|
| 81 |
|
JAIN H323 |
|
H.323 defines a system for moving real-time bi-directional multimedia (video, voice, data, fax, etc.) across packet-based networks. |
|
Withdrawn
|
|
Due to the general absence of interest in the Community, the Specification Lead decided to withdraw the JSR from development. |
|
| Withdrawn |
|
Effective: 2002-02-05 |
|
|
|
Orit Levin, RADvision |
|
| 82 |
|
JavaTM APIs for Bluetooth |
|
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. |
|
Maintenance
|
|
| Maintenance Draft Review 4 |
Download page |
Start: 2010-03-08 |
End: 2010-04-12 |
|
|
Jens Paetzold, Oracle |
|
| 83 |
|
Multiarray package |
|
This JSR proposes a package implementing true rectangular multidimensional arrays for the JavaTM platform. |
|
Withdrawn
|
|
JSR-83 has shown slow progress for several years and has not generated significant industry interest or participation. With no outlook for a timely completion of this JSR, the Spec Lead decided to withdraw it. |
|
| Withdrawn |
|
Effective: 2005-09-06 |
|
|
|
Jose E. Moreira, IBM |
|
| 84 |
|
Floating Point Extensions |
|
This JSR proposes extensions to the JavaTM Programming Language and Java Virtual Machine that support more efficient execution of floating point code. |
|
Withdrawn
|
|
Due to the general absence of interest in the community, the Specification lead withdrew the JSR. |
|
| Withdrawn |
|
Effective: 2002-03-01 |
|
|
|
Marc Snir, IBM |
|
| 85 |
|
Rules-based Authorization and Audit |
|
Define an API for managing and accessing a rules-based authorization and audit trail service. |
|
Rejected
|
|
This JSR was not approved by the SE/EE Executive Committee in the JSR Approval Ballot. |
|
| JSR Review Ballot Failed |
|
Start: 2000-10-10 |
|
|
|
Hal Lockhart, Entegrity Solutions |
|
| 86 |
|
Enterprise Media Beans |
|
Enterprise Media Beans provide a framework to integrate rich media data (i.e. audio, video, or image) into applications based on EJBTM Entity Beans within the J2EETM application development model. |
|
Final
|
|
|
|
Lou Raymundo, Watchmark Corporation |
|
| 87 |
|
JavaTM Agent Services |
|
This specification defines a set of objects and service interfaces to support the deployment and operation of autonomous communicative agents. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. |
|
| Withdrawn |
|
Effective: 2011-01-25 |
|
|
|
Francis G. McCabe, Fujitsu Limited |
|
| 88 |
|
JavaTM EE Application Deployment |
|
This specification provides a complete description of the APIs required by the J2EE platform to enable development of platform-independent deployment tools. |
|
Maintenance
|
|
|
|
Gerald Ingalls, Oracle |
|
| 89 |
|
OSS Service Activation API |
|
Provide an API that allows telecom management applications to be developed and integrated with Java-enabled Service Activation systems. |
|
Final
|
|
|
|
Andreas Ebbert-Karroum, codecentric AG |
|
| 90 |
|
OSS Quality of Service API |
|
Provide an API that allows telecom management applications to be developed and integrated with Java-enabled Quality of Service systems. |
|
Final
|
|
|
|
Ashutosh Sharma, Wipro Technologies |
|
| 91 |
|
OSS Trouble Ticket API |
|
The OSS Trouble Ticket API will provide interfaces for creating, querying, updating, and deleting trouble tickets (trouble reports). |
|
Maintenance
|
|
|
|
Roman Schlegel, Frox Communication |
|
| 92 |
|
Localizable Text |
|
Localizable Text is the infrastructure necessary to translate language-neutral information (in an object) from anywhere in a distributed network. |
|
Withdrawn
|
|
Both JSR-92 and JSR-150 address the issue of 'distributed internationalization' in the J2EE world. JSR-92 is somewhat client-centric in nature while JSR-150 attempts to provide a server-side solution. The progress of JSR-92 is rather slow, and some of the issues raised in JSR-92 can be addressed more elegantly by the technology advocated in JSR-150. The existence of two separate JSRs for the same issue of distributed internationalization can generate unnecessary confusion. Hence we feel JSR-92 should be withdrawn from the JSR space altogether. We will incorporate relevant portions of JSR-92 in JSR-150. |
|
| Withdrawn |
|
Effective: 2005-02-08 |
|
|
|
Debasish Banerjee, IBM |
|
| 93 |
|
JavaTM API for XML Registries 1.0 (JAXR) |
|
JAXR provides an API for a set of distributed Registry Services that enables business-to-business integration between business enterprises, using the protocols being defined by ebXML.org, Oasis, ISO 11179. |
|
Final
|
|
|
|
Paul Sterk, Sun Microsystems, Inc. |
|
| 96 |
|
JavaTM Daemons |
|
The Java Daemon API supplies a small container framework for
developing and deploying independently running services in order to fill the gap caused by different handling on existing native platforms. |
|
Withdrawn
|
|
Following the failed Draft Approval Ballot, the Spec Lead decided not to work on materials for a reconsideration ballot and withdrew the JSR from the Java Community Process. |
|
| Withdrawn |
|
Effective: 2002-03-15 |
|
|
|
Thomas Kopp, Dialogika GMBH |
|
| 97 |
|
JavaHelpTM 2.0 Specification |
|
A major update to the JavaHelp 1.0 Specification, including enhancements to merging, multi-topic printing, improved secondary window and popup usage, JFC ToolTip HelpSet support, HelpSet presentation controls and additional Navigators. |
|
Final
|
|
|
|
Roger Brinkley, Oracle |
|
| 100 |
|
JAINTM Service Creation Environment |
|
JAINTM SCE will support and simplify the creation of portable telecommunication
services delivered primarily to the JAINTM Service Logic Execution Environment, while not restricted to this class of Execution Environments. |
|
Withdrawn
|
|
Withdrawn when the Spec Lead asked to withdraw and no one from the Expert Group was willing to become the new Spec Lead. |
|
| Withdrawn |
|
Effective: 2006-12-04 |
|
|
|
John-Luc Bakker, Telcordia Technologies, Inc. |
|
| 102 |
|
JDOM 1.0 |
|
JDOM is a way to represent an XML document for easy and efficient reading, manipulation, and writing. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. |
|
| Withdrawn |
|
Effective: 2011-03-22 |
|
|
|
Jason Hunter, Hunter, Jason |
|
| 104 |
|
XML Trust Service APIs |
|
This defines a standard set of APIs and a protocol for a "Trust Service", minimizing the complexity of applications using XML Signature. |
|
Withdrawn
|
|
The Java world has moved on since 2001 and the need for this JSR has declined. |
|
| Withdrawn |
|
Effective: 2009-06-11 |
|
|
|
Anthony Nadalin, IBM |
|
| 105 |
|
XML Digital Signature APIs |
|
This defines and incorporates a standard set of high-level implementation-independent APIs for XML digital signatures services. The XML Digital Signature specification is defined by the W3C. |
|
Final
|
|
|
|
Sean Mullan, Sun Microsystems, Inc. |
|
Sean Mullan, Oracle |
|
| 106 |
|
XML Digital Encryption APIs |
|
This JSR is to define a standard set of APIs for XML digital encryption services. This proposal is to
define and incorporate the high level implementation independent Java APIs. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. |
|
| Withdrawn |
|
Effective: 2010-05-04 |
|
|
|
Bruce Rich, IBM |
|
| 107 |
|
JCACHE - Java Temporary Caching API |
|
Specifies API and semantics for temporary, in memory caching of Java
objects, including object creation, shared access, spooling, invalidation,
and consistency across JVM's. |
|
Maintenance
|
|
| Maintenance Review Ballot 2 |
View results |
Start: 2019-03-05 |
End: 2019-03-11 |
|
|
Joseph Fialli, Oracle |
|
Gregory Robert Luck, Luck, Gregory Robert |
|
Brian Oliver, Oracle |
|
Cameron Purdy, Oracle |
|
| 108 |
|
Units Specification |
|
The JavaTM units package
supports programatic unit handling via an abstract Unit class, run-time checking
and conversion, unit arithmetic, unit parsing and formatting, and a units
database. |
|
Withdrawn
|
|
Withdrawn after the Spec Lead left the JCP and none of the Expert Group took over as Spec Lead. |
|
| Withdrawn |
|
Effective: 2004-07-23 |
|
|
|
Steven Emmerson, University Corporation for Atmospheric Research (UCAR) |
|
| 110 |
|
JavaTM APIs for WSDL |
|
JWSDL provides a standard set of Java APIs for representing, manipulating, reading and writing WSDL (Web Services Description Language) documents, including an extension mechanism for WSDL extensibility. |
|
Final
|
|
|
|
Graham C Turrell, IBM |
|
| 111 |
|
JavaTM Services Framework |
|
Provide a specification that clearly defines the lifecycle, configuration, and management of software application services.
The specification will provide a standard mechanism for assembling service components into Java server applications. |
|
Withdrawn
|
|
Withdrawn with the agreement of the Expert Group. |
|
| Withdrawn |
|
Effective: 2003-08-19 |
|
|
|
Berin Loritsch, Loritsch, Berin |
|
| 112 |
|
J2EETM Connector Architecture 1.5 |
|
The J2EE(TM) Connector Architecture 1/5 extends the existing 1.0 specification with new features including asynchronous integration with enterprise information systems, Java Message Service (JMS)
provider pluggability. |
|
Final
|
|
|
|
Binod PG, Sun Microsystems, Inc. |
|
| 113 |
|
JavaTM Speech API 2.0 |
|
This JSR extends the work of the 1.0 JavaTM Speech API, specifying a cross-platform interface to support speech recognizers and synthesizers. |
|
Final
|
|
|
|
Charles Hemphill, EverSpeech, Inc. |
|
| 116 |
|
SIP Servlet API |
|
The SIP Servlet API defines a high-level extension API for SIP servers. It enables SIP applications to be deployed and managed based on the
servlet model. |
|
Final
|
|
|
|
Anders Kristensen, Dynamicsoft, Inc |
|
| 120 |
|
Wireless Messaging API |
|
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. |
|
Final
|
|
|
|
Marquart Franz, Siemens AG |
|
| 121 |
|
Application Isolation API Specification |
|
An API for initiating and controlling computations isolated from each other to varying degrees. Some API semantics are similar to those of
ThreadGroup. |
|
Final
|
|
|
|
Krzysztof Palacz, Sun Microsystems, Inc. |
|
| 122 |
|
JAINTM JCAT |
|
This develops the JavaTM Coordination and Transaction (JCAT) specification, which perceives Java Call Control (JCC) as its core package and extends it with concepts to model and control terminal capabilities. |
|
Withdrawn
|
|
We see no reason to keep it as there has be no development or interest for a long time and we do not intend to further evolve the standard. |
|
| Withdrawn |
|
Effective: 2016-04-05 |
|
|
|
Christer Boberg, Ericsson AB |
|
| 123 |
|
JAINTM Presence and Availability Management (PAM) API |
|
JAINTM SPA Presence and Availability Management API will provide Java APIs to disseminate and manage presence information securely across heterogeneous networks and applications. |
|
Withdrawn
|
|
Withdrawn when no one was found to take over Specification Lead role. In addition, the differences between the OSA PAM and JAIN PAM specs are sufficiently small that it's not clear that the industry benefits from two specifications. |
|
| Withdrawn |
|
Effective: 2004-03-19 |
|
|
|
Jorge Lobo, Teltier Technologies |
|
| 125 |
|
JAINTM SIP Lite |
|
The JAINTM SIP Lite API defines a high level API to the SIP stack to allow for the rapid development of applications. |
|
Withdrawn
|
|
Withdrawn after no one on the Expert Group offered to take over the Spec Lead role. Because of the resourcing issues, Nortel had to withdraw from JSR125. Nortel was unable to provide the RI and the TCK, but believed that this is the right approach for a Proxy and small footprint SIP servers/Clients. |
|
| Withdrawn |
|
Effective: 2006-03-14 |
|
|
|
David Tweedie, Nortel |
|
| 126 |
|
Distributed Page Assembly |
|
This specification defines a standard application model and architecture for distributed page assembly within the J2EE framework. |
|
Withdrawn
|
|
Initial discussions for the JSR 126 EG were deferred when they realized that a viable solution in the proposed direction, which is complimentary to JSR 128, required advancements in the underlying technology (Edge Side Includes). At the time, it seemed that discussion about ESI-related standards were sufficiently active that they could wait for the next version of the standard. However, those discussions seemed to stall as attentions were directed to early adoption and other topics. If ESI standards are revised at a later date, then perhaps the objectives of JSR 126 could be pursued through a new JSR. |
|
| Withdrawn |
|
Effective: 2003-11-10 |
|
|
|
Rajesh Agarwalla, IBM |
|
Steve Ims, IBM |
|
| 127 |
|
JavaServer Faces |
|
This specification defines an architecture and APIs which simplify the creation
and maintenance of Java Server application GUIs. |
|
Final
|
|
|
|
Ed Burns, Oracle |
|
Craig R. McClanahan, Sun Microsystems, Inc. |
|
| 128 |
|
JESI - JSP Tag Library for Edge Side Includes (ESI) |
|
The JESI tag library facilitates the use of Edge Side Include (ESI) in-markup language within JSP applications. JESI tags simplify the declaration of cacheable dynamic fragments, content invalidation and personalization. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. |
|
| Withdrawn |
|
Effective: 2010-02-26 |
|
|
|
Olga Peschansky, Oracle |
|
| 129 |
|
Personal Basis Profile Specification |
|
The J2METM Personal Basis Profile provides a J2ME application environment for network-connected devices supporting a basic level of graphical presentation. |
|
Maintenance
|
|
|
|
Jon Courtney, Sun Microsystems, Inc. |
|
| 130 |
|
OSS Billing Mediation API |
|
Provide an API via the OSS through Java initiative that
allows telecom network management applications to be developed and
integrated with Java-enabled IP Billing systems. |
|
Maintenance
|
|
|
|
Tulika Pradhan, Infozech Software Ltd. |
|
| 131 |
|
ECPerf 1.1 |
|
ECperf 1.1 is a maintenance release of ECperf 1.0. The ECperf 1.1 Expert Group will also be responsible for evaluating and accepting ECperf 1.0 results submitted. |
|
Final
|
|
|
|
Shanti Subramanyam, Sun Microsystems, Inc. |
|
| 132 |
|
JAINTM OAM API Specification v2.0 |
|
This would have developed the JAINTM Operations, Administration, and Maintenance API v2.0 Specification, which defines a standard Interface for provisioning and managing various protocol interfaces, switching platforms, and applications servers. |
|
Withdrawn
|
|
The JAIN community has decided to encapsulate the management functionality for each of the JAIN protocol specifications into their own specification as opposed to encapsulating this functionality in a separate JSR. |
|
| Withdrawn |
|
Effective: 2002-01-28 |
|
|
|
Phelim O'Doherty, Sun Microsystems, Inc. |
|
| 134 |
|
JavaTM Game Profile |
|
Defines a Java 2 Micro Edition Profile for the purposes of game development targeting high-end consumer game devices and desktops. |
|
Withdrawn
|
|
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. |
|
| Withdrawn |
|
Effective: 2003-07-09 |
|
|
|
Bartley Calder, Sun Microsystems, Inc. |
|
| 135 |
|
Mobile Media API |
|
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. |
|
Maintenance
|
|
| Maintenance Draft Review 3 |
Download page |
Start: 2010-09-20 |
End: 2010-10-25 |
|
|
Michael Lagally, Oracle |
|
| 136 |
|
JavaTM Technology for Service Providers |
|
This would have correlated JSRs targeted at next-generation service providers, documented how these JSRs fit together within end-to-end service provider networks, and introduced developers to emerging service provider network-targeted APIs. |
|
Withdrawn
|
|
Community support was not sufficient to support an Expert Group. |
|
| Withdrawn |
|
Effective: 2004-03-19 |
|
|
|
Mauricio Arango, Sun Microsystems, Inc. |
|
| 137 |
|
JAINTM 3G MAP Specification |
|
This JSR is to develop the JAINTM 3G MAP APIs which will enable mobile applications in the 3G domain to talk to each other. |
|
Withdrawn
|
|
Seeing that there has been no active interest in the JAIN 3G Map APIs recently and because of lack of member contributions to the Expert Group, the Spec Lead decided to withdrawn the JSR. |
|
| Withdrawn |
|
Effective: 2003-03-04 |
|
|
|
Sanjiv Kapur, Hughes Software Systems |
|
| 138 |
|
Performance Metric Instrumentation |
|
Specifies standard APIs for performance metric instrumentation of Java programs. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. |
|
| Withdrawn |
|
Effective: 2010-02-26 |
|
|
|
Bruce Irvin, Oracle |
|
| 140 |
|
Service Location Protocol (SLP) API for Java |
|
This JSR is to standardize the Service Location Protocol Application Programmer Interface for Java as described in RFC 2614. |
|
Withdrawn
|
|
The Spec Lead was not doing work on the JSR. While several other organizations have done seemingly promising Java work in the SLP area, none of them was interested in taking over the spec lead position to progress a JSR on it. |
|
| Withdrawn |
|
Effective: 2004-10-05 |
|
|
|
Nick Briers, The SCO Group |
|
| 141 |
|
SDP API |
|
The IETF protocol SDP specifies messages that describe multi-media sessions and are included within other protocol messages as payload. The API will enable users to manipulate SDP messages. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in May 2012. |
|
|
|
Kelvin R Porter, Cisco Systems |
|
| 142 |
|
OSS Inventory API |
|
The OSS Inventory API defines J2EE based interfaces between inventory repositories and other OSS components. |
|
Final
|
|
|
|
Pierre Gauthier, Oracle |
|
| 143 |
|
JavaDesk |
|
JavaDesk provides a standard desktop API across platforms using an MVC model. Applications can control and
enhance the desktop using the JavaDesk API. |
|
Rejected
|
|
This JSR was not approved by the SE/EE Executive Committee in the JSR Approval Ballot. |
|
| Rejected |
|
Effective: 2001-08-06 |
|
|
|
Rich Isaac, Bay Equities, Inc. |
|
| 144 |
|
OSS Common API |
|
This JSR specifies the set of APIs which are common across the OSS through Java JSRs. This provides consistency by reducing duplication of common interfaces and classes among these JSRs. |
|
Maintenance
|
|
|
|
Vincent Perrot, Sun Microsystems, Inc. |
|
| 146 |
|
WBEM Services: JMX Provider Protocol Adapter |
|
JSR-048 defines WBEM support for Java. This specification would have defined how JMX instrumentation mapped to CIM and the definition of a JMX Provider Protocol Adapter for WBEM Services. |
|
Withdrawn
|
|
After a year and a half of no progress, the Spec Lead suggested withdrawing the JSR and the Expert Group did not object. |
|
| Withdrawn |
|
Effective: 2003-07-14 |
|
|
|
Chris Seibel, Sun Microsystems, Inc. |
|
| 148 |
|
3D Media Utilities |
|
The 3D Media Utilities API specifies classes and interfaces for 3D vector
operations and volumetric imaging. |
|
Withdrawn
|
|
After over a year of no development, the Spec Lead suggested withdrawing the JSR and the Expert Group did not object. |
|
| Withdrawn |
|
Effective: 2002-12-02 |
|
|
|
Brian Burkhalter, Sun Microsystems, Inc. |
|
Kevin Rushforth, Sun Microsystems, Inc. |
|
| 149 |
|
Work Area Service for J2EE |
|
The Work Area Service allows J2EE developers to set properties as application context that is implicitly attached to and made
available
anywhere during the processing of remote requests. |
|
Withdrawn
|
|
JSR-149 had shown slow progress for several years and had not generated significant industry interest or participation. With no outlook for a timely completion of this JSR, the Spec Lead withdrew the JSR once no one in the Expert Group agreed to take over the Spec Lead role. |
|
| Withdrawn |
|
Effective: 2005-10-26 |
|
|
|
Heath Thomann, IBM |
|
| 150 |
|
Internationalization Service for J2EE |
|
The Internationalization Service enables distributed localization within Enterprise Java applications by transparently propagating and
managing localization information within relevant J2EE application components. |
|
Withdrawn
|
|
JSR-150 had been idle for several years and the existing draft had not kept pace with changes in J2EE. The Spec Lead wished to withdraw the JSR. None of the EG members objected. |
|
| Withdrawn |
|
Effective: 2008-10-30 |
|
|
|
Charles Hornig, IBM |
|
| 153 |
|
Enterprise JavaBeansTM 2.1 |
|
The Enterprise JavaBeans 2.1 specification adds to the EJB
architecture support for web services, extensions to message-driven beans, enhancements to EJB QL, and a container-managed timer service. |
|
Final
|
|
|
|
Linda Demichiel, Oracle |
|
| 154 |
|
JavaTM Servlet 2.4 Specification |
|
This specification will build on servlet specification version 2.3 by enhancing existing features and adding new facilities of a reasonably small
nature. |
|
Maintenance
|
|
|
|
Rajiv Mordani, Oracle |
|
| 155 |
|
Web Services Security Assertions |
|
To provide a set of APIs, exchange patterns & implementation to securely (integrity and confidentiality) exchange assertions between web
services based on OASIS SAML. |
|
Withdrawn
|
|
Withdrawn by the JSR 155 Spec Lead due to changing industry focus and continued JSR inactivity. |
|
| Withdrawn |
|
Effective: 2010-02-18 |
|
|
|
Sandeep Kumar, Cisco Systems |
|
Krishna Sankar, Cisco Systems |
|
| 156 |
|
Java API for XML Transactions |
|
JAXTX provides an API for packaging and transporting ACID transactions (as
in JTA) and extended transactions (e.g., the BTP from OASIS) using the
protocols being defined by OASIS, W3C. |
|
Withdrawn
|
|
Withdrawn at the request of the Spec Lead. |
|
| Withdrawn |
|
Effective: 2010-02-18 |
|
|
|
Jonathan Halliday, Red Hat |
|
| 157 |
|
ebXML CPP/A APIs for Java |
|
This JSR is to provide a standard set of APIs for representing and manipulating Collaboration Profile and Agreement information described by ebXML CPP/A (Collaboration Protocol Profile/Agreement)documents. |
|
Withdrawn
|
|
Withdrawn at the request of the Spec Lead. |
|
| Withdrawn |
|
Effective: 2010-07-30 |
|
|
|
Himagiri Mukkamala, Sybase |
|
| 158 |
|
JavaTM Stream Assembly |
|
TheJavaTM Stream Assembly API specifies classes and interfaces for the creation, management, and processing of broadcast and interactive stream multiplexes. |
|
Withdrawn
|
|
Withdrawn at the request of the Spec Lead. |
|
| Withdrawn |
|
Effective: 2011-12-14 |
|
|
|
Gerard Fernando, Sun Microsystems, Inc. |
|
| 160 |
|
JavaTM Management Extensions (JMX) Remote API |
|
This API extends the JMX 1.2 API to provide remote access to JMX MBean servers. |
|
Withdrawn
|
|
Withdrawn following Maintenance Review 3. |
|
| Withdrawn |
|
Effective: 2014-03-05 |
|
|
|
Eamonn McManus, Oracle |
|
Simon Vienot, Sun Microsystems, Inc. |
|
Hinkmond Wong, Oracle |
|
| 161 |
|
JAINTM ENUM API Specification |
|
The JAINTM ENUM API Specification defines a standard, portable application programming interface to query and provision E.164 telephone numbers and
their service-specific Uniform Resource Identifiers (URI). |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in May 2012. |
|
|
|
Christopher John, NetNumber, Inc. |
|
| 162 |
|
Portlet API |
|
The Portlet API specification defines an API for components being aggregated in web applications like portals. It includes portlets, portlet container behavior, portlet
windows, events, persistent storage and portlet services. |
|
Withdrawn
|
|
Portlet API As there is very significant overlap between JSRs 162 & 167, Sun and IBM have reached a mutual agreement regarding the proposals. We have now reached a point where we feel that we have a mutually acceptable new combined JSR proposal, which we now wish to seek endorsement of from the existing supporters of JSR 162 and 167. |
|
| Withdrawn |
|
Effective: 2002-01-20 |
|
|
|
Stefan Hepper, IBM |
|
| 164 |
|
SIMPLE Presence |
|
SIMPLE Presence provides a standard portable and secure interface to manipulate presence information between a SIMPLE client (watcher) and a presence server (presence agent). |
|
Final
|
|
|
|
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory |
|
| 165 |
|
SIMPLE Instant Messaging |
|
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. |
|
Final
|
|
|
|
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory |
|
| 166 |
|
Concurrency Utilities |
|
The JSR proposes a set of medium-level utilities that provide
functionality commonly needed in concurrent programs. |
|
Final
|
|
|
|
Doug Lea, Lea, Doug |
|
| 167 |
|
JavaTM Portlet Specification |
|
This specification would have defined a set of APIs for Portal computing addressing the areas of aggregation, personalization, presentation and security. |
|
Withdrawn
|
|
As there is very significant overlap between JSRs 162 & 167, Sun and IBM reached a mutual agreement regarding the proposals. They reached a point where they felt that they had a mutually acceptable new combined JSR proposal, which they then sought endorsement of from the existing supporters of JSR 162 and 167. |
|
| Withdrawn |
|
Effective: 2002-01-20 |
|
|
|
Alejandro Abdelnur, Sun Microsystems, Inc. |
|
Wesley Budziwojski, Sun Microsystems, Inc. |
|
| 168 |
|
Portlet Specification |
|
To enable interoperability between Portlets and Portals, this specification will define a set of APIs for Portal computing addressing the areas of aggregation, personalization, presentation and security. |
|
Final
|
|
|
|
Martin Nicklous, IBM |
|
| 173 |
|
Streaming API for XML |
|
The Streaming API for XML (StAX) is a Java based API for pull-parsing XML. |
|
Withdrawn
|
|
Since version 1.0, JSR 173 StAX API has been distributed as both a standalone technology and part of the Java SE. The API has been stable without any significant changes since then and the need to use newer releases of the StAX API with shipping releases of Java SE has mostly disappeared in recent years.
In accordance with JCP 2.10 Process Document, 3.3.1.4 Platform inclusion, we are announcing the end of JSR 173 StAX Standalone distribution. After MR5, StAX 1.4, the technology that JSR 173 defines will be delivered as a part of the Java SE solely. Future changes in the StAX API will be defined through the Platform JSR.
The subsumption of the StAX API into the Platform JSR does not change any mechanisms defined in StAX. The service provider interfaces are the same except that they will then be directly specified in the Platform JSR. Deployment of alternative implementations of the StAX APIs will continue to be supported. |
|
| Withdrawn |
|
Effective: 2016-07-26 |
|
|
|
Christopher Fry, BEA Systems |
|
Devasena Sagar, Oracle |
|
| 178 |
|
Mobile Game API |
|
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. |
|
Rejected
|
|
This JSR was not approved by the ME Executive Committee in the JSR Reconsideration Ballot. |
|
| Rejected |
|
Effective: 2002-05-07 |
|
|
|
Thomas Landspurg, In-Fusio SA |
|
| 179 |
|
Location API for J2METM |
|
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. |
|
Final
|
|
|
|
Kimmo Loytana, North Sixty-One Ltd |
|
Cheng Wang, Nokia Corporation |
|
| 180 |
|
SIP API for J2METM |
|
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. |
|
Final
|
|
|
|
Erkki Rysä, North Sixty-One Ltd |
|
Cheng Wang, Nokia Corporation |
|
| 182 |
|
JPay - Payment API for the JavaTM Platform |
|
This JSR requests the creation of the Payment API for the Java Platform (JPay) specification. The JPay API will support payments in an open, Web-like environment. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in May 2012. |
|
| Early Draft Review |
Download page |
Start: 2004-10-27 |
End: 2004-12-25 |
|
|
Marquart Franz, Siemens AG |
|
| 183 |
|
Web Services Message Security APIs |
|
This JSR is to define a standard set of APIs for Web services message security. The goal of this JSR is to enable applications to construct secure SOAP message exchanges. |
|
Withdrawn
|
|
Web services security (WS-Security) has become the defacto standard to secure web services messages. Lack of a standard in Java to write to these APIs, hasn't caused any interoperability or integration issues across vendor platforms. So, this JSR was withdrawn. |
|
| Withdrawn |
|
Effective: 2008-08-05 |
|
|
|
Nataraj Nagaratnam, IBM |
|
| 184 |
|
Mobile 3D Graphics API for J2METM |
|
This proposed JSR will provide a scalable, small-footprint, interactive 3D API for use on mobile devices. |
|
Final
|
|
|
|
Tomi Aarnio, Nokia Corporation |
|
Erkki Rysä, North Sixty-One Ltd |
|
| 186 |
|
Presence |
|
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. |
|
Final
|
|
|
|
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory |
|
| 187 |
|
Instant Messaging |
|
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. |
|
Final
|
|
|
|
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory |
|
| 188 |
|
CC/PP Processing |
|
To enable interoperability between web servers and access mechanisms, and to facilitate development of device independent web applications, this specification will define a set of APIs for processing CC/PP information. |
|
Final
|
|
|
|
Nigel Jacobs, Oracle |
|
Jerry Raj, Sun Microsystems, Inc. |
|
| 189 |
|
JavaTM 3D API 1.4 |
|
This JSR will add new large scale funtionality to Java 3D. Possible technologies for inclusion include programmable shading and advanced rendering techniques. |
|
Withdrawn
|
|
The changes to the Java 3D API as originally envisioned by JSR-189 were quite significant, and were planned as part of a major API release, for which we had planned to form an expert group under the JSR. Due to changes in the nature of the project development, this effort was discontinued in 2002, a few months after the JSR was filed. JSR-189 was left open as a place-holder, but it no longer makes sense to leave it open. At the time of withdrawal, the Java 3D API was a community source project on java.net, where all new development had happened over the past 18 months. They were actively developing the 1.4 API release with help from the Java 3D community on java.net. This release was a much more modest undertaking than was originally planned, and all new API changes are being designed with public input. As such they closed this JSR, and did Java 3D 1.4 as a maintenance release under the JCP. |
|
| Withdrawn |
|
Effective: 2005-11-08 |
|
|
|
Kevin Rushforth, Sun Microsystems, Inc. |
|
| 190 |
|
Event Tracking API for J2ME |
|
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. |
|
Final
|
|
|
|
Shai Gotlib, Amdocs Management Ltd. |
|
| 192 |
|
JAINTM Service Creation Environment - JavaTM PART |
|
This is the specification for the JavaTM API to support and simplify the creation of portable telecommunication services delivered primarily to the JAINTM
Service Logic Execution Environment (JAINTM SLEE). |
|
Withdrawn
|
|
There had not been much progress on this JSR since quite some time. The draft was floated for Expert Group review but there was no response even after several reminders. They then decided not to go ahead with this activity and hence requested the PMO to mark this JSR 192 as WITHDRAWN. |
|
| Withdrawn |
|
Effective: 2004-09-22 |
|
|
|
Vishal Aggarwal, Hughes Software Systems |
|
| 193 |
|
Client Side Container (CSC) |
|
This would have described a client-side container architecture, providing common client infrastructure, for developing API-neutral clients (Swing, AWT, Command Line). The access to J2EE-components would be fully abstracted and encapsulated. |
|
Withdrawn
|
|
Having noticed the many questions/concerns about this specification proposal, the submitter decided to withdraw the request. |
|
| Withdrawn |
|
Effective: 2002-10-14 |
|
|
|
Adam Bien, Bien, Adam |
|
| 194 |
|
JAINTM ULS API |
|
This was intended to allow software developers to rapidly develop external Service Provider-type applications to interrogate the location and status of a user's mobile device. |
|
Withdrawn
|
|
With agreement from his Expert Group, the Spec Lead decided to withdrawn this JSR following decisions at the November 2002 JAIN meeting in Austin. |
|
| Withdrawn |
|
Effective: 2003-02-21 |
|
|
|
Jorgen Dyst, Appium Technologies AB |
|
| 195 |
|
Information Module Profile |
|
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. |
|
Final
|
|
|
|
Thomas Lampart, Cinterion Wireless Modules GmbH |
|
Jari Lansio, Nokia Corporation |
|
| 199 |
|
JavaTM Compiler API |
|
A service provider API that allows a Java program to select
and invoke a Java Language Compiler programmatically. |
|
Maintenance
|
|
|
|
Jonathan Gibbons, Oracle |
|
| 200 |
|
Network Transfer Format for JavaTM Archives. |
|
This JSR will define a dense download format for JavaTM classfiles. It is expected that this format can achieve considerable size savings over compressed JAR files. |
|
Final
|
|
|
|
John Rose, Sun Microsystems, Inc. |
|
Kumar Srinivasan, Sun Microsystems, Inc. |
|
| 202 |
|
JavaTM Class File Specification Update |
|
This JSR will make incremental updates to the JavaTM class file format. This will principally consist of increasing certain class file size limits and adding support for split verification. |
|
Final
|
|
|
|
Alex Buckley, Oracle |
|
| 204 |
|
Unicode Supplementary Character Support |
|
The proposed specification will define a mechanism to support Supplementary Characters as defined in the Unicode 3.1 specification. |
|
Final
|
|
|
|
Masayoshi Okutsu, Sun Microsystems, Inc. |
|
| 206 |
|
JavaTM API for XML Processing (JAXP) 1.3 |
|
JAXP 1.3 is the next version of JAXP, an implementation independent portable API for processing XML with JavaTM. |
|
Withdrawn
|
|
Withdrawn following Maintenance Review 3. |
|
| Withdrawn |
|
Effective: 2014-03-05 |
|
|
|
Jeff Suttor, Sun Microsystems, Inc. |
|
Joe Wang, Oracle |
|
| 207 |
|
Process Definition for JavaTM |
|
Definition of an annotated Java syntax and APIs for programming business processes in Java. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. |
|
| Withdrawn |
|
Effective: 2010-02-26 |
|
|
|
Michael Rowley, BEA Systems |
|
| 210 |
|
OSS Service Quality Management API |
|
Provide an API via the OSS through Java initiative that allows telecom management applications to be developed and integrated with Java-enabled Service Quality Management Systems. |
|
Withdrawn
|
|
The API has been completed and contributed to TMF and there is no reason to continue with the JSR. |
|
| Withdrawn |
|
Effective: 2012-05-23 |
|
|
|
Thierry Supplisson, IBM |
|
| 211 |
|
Content Handler API |
|
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. |
|
Maintenance
|
|
|
|
Roger Riggs, Oracle |
|
| 213 |
|
Micro WSCI Framework for J2ME. |
|
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. |
|
Rejected
|
|
This JSR was not approved by the ME Executive Committee in the JSR Approval Ballot. |
|
| Rejected |
|
Effective: 2003-05-13 |
|
|
|
Ash Parikh, IOPSIS Software Inc. |
|
| 214 |
|
Micro BPSS for J2ME Devices. |
|
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. |
|
Rejected
|
|
This JSR was not approved by the ME Executive Committee in the JSR Approval Ballot. |
|
| Rejected |
|
Effective: 2003-05-13 |
|
|
|
Ash Parikh, IOPSIS Software Inc. |
|
| 216 |
|
Personal Profile 1.1 |
|
This JSR will update the existing Personal Profile (JSR-62) specification to reflect the J2SETM 1.4 APIs). |
|
Maintenance
|
|
|
|
Jon Courtney, Sun Microsystems, Inc. |
|
Roger Riggs, Oracle |
|
| 218 |
|
Connected Device Configuration (CDC) 1.1 |
|
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. |
|
Maintenance
|
|
|
|
Roger Riggs, Oracle |
|
| 219 |
|
Foundation Profile 1.1 |
|
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. |
|
Maintenance
|
|
|
|
Roger Riggs, Oracle |
|
| 220 |
|
Enterprise JavaBeansTM 3.0 |
|
The purpose of Enterprise JavaBeans (EJB) 3.0 is to improve the EJB architecture by reducing its complexity from the developer's point of view. |
|
Maintenance
|
|
| Maintenance Draft Review |
Download page |
Start: 2007-11-14 |
End: 2007-12-17 |
|
|
Linda Demichiel, Oracle |
|
Mike Keith, Oracle |
|
| 221 |
|
JDBCTM 4.0 API Specification |
|
This specification seeks to improve Java application access to SQL data stores by the provision of ease-of-development focused features and improvements at both the utility and API level. |
|
Maintenance
|
|
|
|
Lance Andersen, Oracle |
|
| 223 |
|
Scripting for the JavaTM Platform |
|
The specification will describe mechanisms allowing scripting language programs to access information developed in the Java Platform and allowing scripting language pages to be used in Java Server-side Applications. |
|
Withdrawn
|
|
Withdrawn in December 2016 following the Maintenance Review. |
|
| Withdrawn |
|
Effective: 2016-12-13 |
|
|
|
Sundararajan Athijegannathan, Oracle |
|
Mike Grogan, Sun Microsystems, Inc. |
|
| 225 |
|
XQuery API for JavaTM (XQJ) |
|
Develop a common API that allows an application to submit queries conforming to the W3C XQuery 1.0 specification and to process the results of such queries. |
|
Final
|
|
|
|
Maxim Orgiyan, Oracle |
|
Marc Van Cappellen, DataDirect Technologies |
|
| 226 |
|
Scalable 2D Vector Graphics API for J2METM |
|
This specification will define an optional package API for rendering scalable 2D vector graphics, including image files in W3C Scalable Vector Graphics (SVG) format. |
|
Maintenance
|
|
|
|
Juha Eskelinen, Nokia Corporation |
|
Kimmo Loytana, North Sixty-One Ltd |
|
| 229 |
|
Payment API |
|
Enabling application developers to initiate mobile payment transactions in J2METM applications. |
|
Maintenance
|
|
|
|
Jean-Yves Bitterlich, Oracle |
|
| 230 |
|
Data Sync API |
|
Enabling J2METM applications to access native data synchronization implementation |
|
Dormant
|
|
The Specification Lead chose to list this JSR as dormant in August 2011. |
|
|
|
Jens Paetzold, Oracle |
|
| 232 |
|
Mobile Operational Management |
|
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. |
|
Maintenance
|
|
|
|
Venkat Amirisetty, Motorola |
|
Cheng Wang, Nokia Corporation |
|
| 234 |
|
Advanced Multimedia Supplements |
|
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. |
|
Maintenance
|
|
|
|
Erkki Rysä, North Sixty-One Ltd |
|
Cheng Wang, Nokia Corporation |
|
| 235 |
|
Service Data Objects |
|
Defines core infrastructure APIs for heterogeneous data access that supports common application design patterns and supports higher-level tools and frameworks. |
|
Final
|
|
|
|
Kelvin Goodson, IBM |
|
Radu Preotiuc-Pietro, Oracle |
|
| 236 |
|
Concurrency Utilities for JavaTM EE |
|
Concurrency Utilities for Java EE provides a simple, standardized API for using concurrency from application components without compromising container integrity while still preserving the Java EE platform's fundamental benefits. |
|
Final
|
|
|
|
Anthony Lai, Oracle |
|
| 237 |
|
Work Manager for Application Servers |
|
A work manager API providing for execution of concurrent work items within managed environments. |
|
Withdrawn
|
|
JSR 237 has been merged with JSR 236, providing a single, consistent specification for Java EE concurrency. |
|
| Withdrawn |
|
Effective: 2008-06-18 |
|
|
|
Chris D Johnson, IBM |
|
Naresh Revanuru, BEA Systems |
|
| 238 |
|
Mobile Internationalization API |
|
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. |
|
Final
|
|
|
|
Jere Kapyaho, Nokia Corporation |
|
Erkki Rysä, North Sixty-One Ltd |
|
| 240 |
|
JAINTM SLEE (JSLEE) v1.1 |
|
This JSR is a logical extension to address gaps in JSLEE v1.0 specification. The central area of focus is to specify the Resource Adaptor Architecture API and semantics. |
|
Final
|
|
|
|
David Ferry, Open Cloud Limited |
|
| 241 |
|
The Groovy Programming Language |
|
Groovy is an agile, dynamic programming language for the Java Virtual Machine. Groovy includes features found in Python, Ruby, and Smalltalk, but uses syntax similar to the Java programming language. |
|
Dormant
|
|
The Specification Lead chose to list this JSR as dormant in April 2012. |
|
| Expert Group Formation |
|
Start: 2004-03-30 |
|
|
|
No Current Spec Lead, No SL Company |
|
| 242 |
|
Digital Set Top Box Profile - "On Ramp to OCAP" |
|
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. |
|
Final
|
|
|
|
Donald Bleyl, Cox Communications, Inc. |
|
Jens Paetzold, Oracle |
|
| 245 |
|
JavaServerTM Pages 2.1 |
|
This is the next revision of the JavaServerTM Pages specification. The purpose of JSP 2.1 is to improve alignment with JavaServerTM Faces (JSF) and enhance ease of development. |
|
Maintenance
|
|
|
|
Kinman Chung, Oracle |
|
| 246 |
|
Device Management API |
|
Enabling J2METM applications to access device management implementations |
|
Dormant
|
|
The Specification Lead chose to list this JSR as dormant in August 2011. |
|
| Early Draft Review |
Download page |
Start: 2005-08-08 |
End: 2005-09-07 |
|
|
Jens Paetzold, Oracle |
|
| 247 |
|
Data Mining 2.0 |
|
JDM 2.0 will address requested features deferred from JDM 1.0, which focused on the data mining framework and a select number of mining functions and algorithms. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. |
|
| Withdrawn |
|
Effective: 2011-05-02 |
|
|
|
Mark F. Hornick, Oracle |
|
| 248 |
|
Mobile Service Architecture |
|
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. |
|
Maintenance
|
|
|
|
Guenter Klas, Vodafone Group Services Limited |
|
Erkki Rysa, Nokia Corporation |
|
| 249 |
|
Mobile Service Architecture 2 |
|
This JSR defines the next generation of the Mobile Service Architecture and platform created in JSR 248. |
|
Dormant
|
|
The Specification Leads chose to list this JSR as dormant in August 2012. |
|
| Public Review Ballot |
View results |
Start: 2009-02-17 |
End: 2009-02-23 |
|
|
Adamu Haruna, Nokia Corporation |
|
Guenter Klas, Vodafone Group Services Limited |
|
| 251 |
|
Pricing API |
|
Standard for defining and using complex pricing data and business rules, enabling integration, allowing business differentiating extensions. Addresses usage-based business model needs, for communications and entertainment industries and utilities. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in May 2012. |
|
| Early Draft Review |
Download page |
Start: 2006-05-01 |
End: 2006-05-31 |
|
|
No Current Spec Lead, No SL Company |
|
| 252 |
|
JavaServer Faces 1.2 |
|
This JSR is an update to the 1.1 version of the JavaServer Faces specification. Its scope goes beyond a JCP maintenance release, but is short of a new feature release. |
|
Maintenance
|
|
| Maintenance Draft Review 3 |
Download page |
Start: 2008-07-22 |
End: 2008-08-25 |
|
|
Ed Burns, Oracle |
|
Roger Kitain, Oracle |
|
| 253 |
|
Mobile Telephony API (MTA) |
|
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. |
|
Final
|
|
|
|
Jean-Yves Bitterlich, Oracle |
|
Brian Deuser, Motorola |
|
| 254 |
|
OSS Discovery API |
|
Provide an API that allows network discovery applications to be developed and integrated with other OSS/J enabled applications. |
|
Final
|
|
|
|
Andrew Paterson, Nakina Systems |
|
Sergio Pellizzari, Nakina Systems |
|
Yves Thibeault, Nakina Systems |
|
| 255 |
|
JavaTM Management Extensions (JMXTM) Specification, version 2.0 |
|
This JSR updates the JMX and JMX Remote APIs for version 6.0 of the Java(TM) Platform, Standard Edition. It will improve usability of existing features and add new functionality. |
|
Withdrawn
|
|
JSR 255 specified changes to javax.management.* which were subsequently abandoned due to lack of resources, and were not included in the Java SE 6 or 7 Platforms. (The changes were distinct from other changes to javax.management.* specified by JSRs 3, 160, and 336 for inclusion in the Java SE 6 and 7 Platforms.) It was determined in 2014 that future changes to JMX technology would be specified directly by the umbrella JSR for the Java SE Platform. |
|
| Withdrawn |
|
Effective: 2016-03-24 |
|
|
|
Staffan Larsen, Oracle |
|
| 256 |
|
Mobile Sensor API |
|
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. |
|
Maintenance
|
|
| Maintenance Draft Review 4 |
Download page |
Start: 2009-03-27 |
End: 2009-04-27 |
|
|
Kimmo Loytana, North Sixty-One Ltd |
|
Pia Niemela, Nokia Corporation |
|
| 257 |
|
Contactless Communication API |
|
This specification will define J2ME Optional Packages for contactless communication, one package for bi-directional communication and the other for accessing read-only information. |
|
Maintenance
|
|
|
|
Kimmo Loytana, North Sixty-One Ltd |
|
Jaana Majakangas, Nokia Corporation |
|
| 258 |
|
Mobile User Interface Customization API |
|
The Mobile User Interface Customization API provides a way to query and modify the user interface customization properties of a mobile device or platform. |
|
Maintenance
|
|
|
|
Jere Kapyaho, Nokia Corporation |
|
Erkki Rysä, North Sixty-One Ltd |
|
| 259 |
|
Ad Hoc Networking API |
|
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. |
|
Dormant
|
|
The Specification Lead chose to list this JSR as dormant in August 2011. |
|
| Early Draft Review |
Download page |
Start: 2006-01-30 |
End: 2006-03-01 |
|
|
Volker Bauche, Oracle |
|
| 260 |
|
JavadocTM Tag Technology Update |
|
Defines new tags and generated Javadoc document representation aimed
to increase readability, information richness, and make the Javadoc
more approachable to developers learning and using the APIs. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. |
|
| Withdrawn |
|
Effective: 2011-03-22 |
|
|
|
Danny Coward, Oracle |
|
| 261 |
|
JavaTM API for XML Web Services Addressing (JAX-WSA) |
|
The Java API for XML Web Services Addressing (JAX-WSA) 1.0 specification will define APIs and a framework for supporting transport-neutral addressing of Web services. |
|
Withdrawn
|
|
All the work done under this JSR has been subsumed under JSR 224. This was conveyed to the EG at earlier instances as well and nobody objected. |
|
| Withdrawn |
|
Effective: 2006-12-15 |
|
|
|
Mike Grogan, Sun Microsystems, Inc. |
|
Arun Gupta, Sun Microsystems, Inc. |
|
| 262 |
|
Web Services Connector for Java Management Extensions (JMX) Agents |
|
Defines a connector for the JMX Remote API that uses Web Services to make JMX instrumentation available remotely. Clients do not have to be Java applications, but can be. |
|
Withdrawn
|
|
JSR 262 specified the javax.management.remote.ws API which was subsequently abandoned due to lack of resources, and was not included in the Java SE 7 Platform. It was determined in 2014 that future changes to JMX technology would be specified directly by the umbrella JSR for the Java SE Platform. |
|
| Withdrawn |
|
Effective: 2016-03-24 |
|
|
|
Staffan Larsen, Oracle |
|
| 263 |
|
Fault Management API |
|
The Fault Management API provides for the monitoring and management of alarms within an information or a telecommunications network. |
|
Final
|
|
|
|
Marc Flauw, Hewlett-Packard |
|
| 264 |
|
Order Management API |
|
This JSR defines an interface to an Order Management component, with specific extensions for activation and work order management use-cases. |
|
Final
|
|
|
|
Andreas Ebbert-Karroum, codecentric AG |
|
| 265 |
|
API for Utilizing Web Services Policy |
|
This specification aims to standardize a basic framework in Java for utilizing the Web services constraints and capabilities. |
|
Withdrawn
|
|
The standardization of policy-based metadata will continue as part of the Service Component Architecture (SCA), which will eventually provide Java-based language bindings as part of separate JSRs. |
|
| Withdrawn |
|
Effective: 2010-01-28 |
|
|
|
Sanjay Patil, SAP SE |
|
Umit Yalcinalp, SAP SE |
|
| 266 |
|
Unified Message Box Access API (UMBA-API) |
|
The purpose of this JSR is to define an API to access and manage the message boxes of the mobile device and their content. |
|
Dormant
|
|
The Specification Lead chose to list this JSR as dormant in May 2012. |
|
| Early Draft Review |
Download page |
Start: 2006-04-14 |
End: 2006-05-14 |
|
|
Michael Lagally, Oracle |
|
| 267 |
|
JSP Tag Library for Web Services |
|
JSPTM Tag Library for accessing Web Services |
|
Withdrawn
|
|
Lack of resources to drive this JSR, produce the RI (Reference Implementation) and TCK (Technology Compatibility Kit)- Waning interest and lack of support for this technology from the community led to the withdrawal of this JSR. |
|
| Withdrawn |
|
Effective: 2008-02-06 |
|
|
|
Dhiru Pandey, Sun Microsystems, Inc. |
|
| 269 |
|
Pluggable Annotation Processing API |
|
Provide an API to allow the processing of JSR 175 annotations (metadata); this will require modeling elements of the Java(TM)
programming language as well as processing-specific functionality. |
|
Active
|
|
|
|
Joe Darcy, Oracle |
|
| 271 |
|
Mobile Information Device Profile 3 |
|
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. |
|
Final
|
|
|
|
Roger Riggs, Oracle |
|
| 272 |
|
Mobile Broadcast Service API for Handheld Terminals |
|
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. |
|
Final
|
|
|
|
Kimmo Loytana, North Sixty-One Ltd |
|
Antti Rantalahti, Nokia Corporation |
|
Ivan Wong, Motorola |
|
| 273 |
|
Design-Time API for JavaBeansTM JBDT |
|
This JSR extends the JavaBeans specification and APIs to improve design-time functionality for component authors to leverage within the visual design environments in IDEs. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. |
|
| Withdrawn |
|
Effective: 2011-03-22 |
|
|
|
Tor Norbye, Oracle |
|
| 274 |
|
The BeanShell Scripting Language |
|
This specification will standardize BeanShell, a Java syntax compatible
scripting language for the Java platform. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in June 2011. |
|
| Expert Group Formation |
|
Start: 2005-06-07 |
|
|
|
Patrick Niemeyer, Niemeyer, Patrick D. |
|
| 275 |
|
Units Specification |
|
This JSR specifies Java packages for modeling and working with standard measures known as units. |
|
Rejected
|
|
This JSR was not approved by the SE/EE Executive Committee in the Public Draft Reconsideration Ballot. |
|
| Rejected |
|
Effective: 2010-03-09 |
|
|
|
Jean-Marie Dautelle, Dautelle, Jean-Marie |
|
Werner Keil, Keil, Werner |
|
| 277 |
|
JavaTM Module System |
|
The specification defines a distribution format and a repository for collections of Java code and related resources. It also defines the discovery, loading, and integrity mechanisms at runtime. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. Superseded by JSR 376. |
|
| Withdrawn |
|
Effective: 2016-01-20 |
|
|
|
Alex Buckley, Oracle |
|
| 278 |
|
Resource Management API for JavaTM ME |
|
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. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in May 2012. |
|
| Public Review Ballot |
View results |
Start: 2007-01-30 |
End: 2007-02-05 |
|
|
Ho An, Samsung Electronics Corporation |
|
Hobum (Vincent) Kwon, Samsung Electronics Corporation |
|
| 279 |
|
Service Connection API for JavaTM ME |
|
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. |
|
Final
|
|
|
|
Kimmo Loytana, North Sixty-One Ltd |
|
Pia Niemela, Nokia Corporation |
|
Jens Paetzold, Oracle |
|
| 280 |
|
XML API for JavaTM ME |
|
This JSR provides a common general purpose XML API for the next generation of mobile devices. |
|
Final
|
|
|
|
Jean-Yves Bitterlich, Oracle |
|
Pia Niemela, Nokia Corporation |
|
| 281 |
|
IMS Services API |
|
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. |
|
Maintenance
|
|
|
|
Piotr Kessler, Ericsson AB |
|
Stefan Svenberg, Ericsson AB |
|
| 284 |
|
Resource Consumption Management API |
|
The API will allow for partitioning resources (constraints, reservations) among Java applications and for querying about resource availability (notifications). It will also provide means of exposing various kinds of resources. |
|
Final
|
|
|
|
Grzegorz Czajkowski, Google Inc. |
|
| 285 |
|
Performance Management API |
|
The Performance Management API provides for the monitoring and management of the performance of an information or telecommunications network. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in June 2011. |
|
| Expert Group Formation |
|
Start: 2005-11-15 |
|
|
|
Dave Raymer, Motorola |
|
| 286 |
|
Portlet Specification 2.0 |
|
Version 2.0 of the Portlet Specification plans to align with J2EE 1.4, integrate other new JSRs relevant for the portlet, and align with the WSRP specification V 2.0. |
|
Maintenance
|
|
| Maintenance Review Ballot |
View results |
Start: 2015-08-18 |
End: 2015-08-24 |
|
|
Martin Nicklous, IBM |
|
| 287 |
|
Scalable 2D Vector Graphics API 2.0 for Java METM |
|
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. |
|
Final
|
|
|
|
Juha Eskelinen, Nokia Corporation |
|
Kimmo Loytana, North Sixty-One Ltd |
|
| 288 |
|
Adaptive JavaTM ME System API |
|
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. |
|
Rejected
|
|
This JSR was not approved by the ME Executive Committee in the JSR Approval Ballot and JSR Reconsideration Ballot. |
|
| Rejected |
|
Effective: 2006-02-22 |
|
|
|
Andre Kruetzfeldt, Aplix Corporation |
|
| 289 |
|
SIP Servlet v1.1 |
|
This specification is an enhancement to the SIPServlet specification. The central focus of this JSR is to enhance the existing SIPServlet specification with new requirements determined by the industry. |
|
Final
|
|
|
|
Yannis Cosmadopoulos, Oracle |
|
Amitha Pulijala, Oracle |
|
| 290 |
|
JavaTM Language & XML User Interface Markup Integration |
|
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. |
|
Dormant
|
|
The Specification Lead chose to list this JSR as dormant in August 2012. |
|
|
|
Jean-Yves Bitterlich, Oracle |
|
| 291 |
|
Dynamic Component Support for JavaTM SE |
|
Establish a JCP specification for a dynamic component framework supporting existing Java SE environments based on the OSGi dynamic component model specifications. |
|
Final
|
|
|
|
Thomas Watson, IBM |
|
| 293 |
|
Location API 2.0 |
|
This specification defines an optional package that enables the developers to use new enhanced location-based features on the JavaTM ME devices. |
|
Final
|
|
|
|
Kimmo Loytana, North Sixty-One Ltd |
|
Jaana Majakangas, Nokia Corporation |
|
| 295 |
|
Beans Binding |
|
Provide an API that allows two properties of two beans to stay in sync. |
|
Withdrawn
|
|
Withdrawn at the request of the Specification Lead. |
|
| Withdrawn |
|
Effective: 2011-05-02 |
|
|
|
Peter Zhelezniakov, Sun Microsystems, Inc. |
|
| 296 |
|
Swing Application Framework |
|
This JSR will provide a simple application framework for Swing applications. It will define infrastructure common to most desktop applications. In so doing, Swing applications will be easier to create. |
|
Withdrawn
|
|
Withdrawn at the Spec Lead's request. |
|
| Withdrawn |
|
Effective: 2011-06-06 |
|
|
|
Alexander Potochkin, Sun Microsystems, Inc. |
|
| 297 |
|
Mobile 3D Graphics API 2.0 |
|
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. |
|
Dormant
|
|
The Specification Leads chose to list this JSR as dormant in June 2013. |
|
|
|
Tomi Aarnio, Nokia Corporation |
|
Erkki Rysä, North Sixty-One Ltd |
|
| 298 |
|
Telematics API for JavaTM ME |
|
This JSR defines the API set for Telematics Service on mobile devices. |
|
Final
|
|
|
|
Dave Kim, SK Telecom Co., Ltd. |
|
Young Min Park, SK Telecom Co., Ltd. |
|
| 300 |
|
DRM API for JavaTM ME |
|
This specification will define an optional package for developing JavaTM ME applications which
utilize or interoperate with DRM agents that separately exist in devices. |
|
Final
|
|
|
|
Jea Un Kim, LG Electronics Inc. |
|
Dnyanesh R Pathak, LG Electronics Inc. |
|
| 302 |
|
Safety Critical JavaTM Technology |
|
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. |
|
Active
|
|
| Public Review Ballot |
View results |
Start: 2021-05-11 |
End: 2021-05-24 |
|
|
C. Douglass Locke, The Open Group |
|
| 303 |
|
Bean Validation |
|
This JSR will define a meta-data model and API for JavaBeanTM validation based on annotations, with overrides and extended meta-data through the use of XML validation descriptors. |
|
Final
|
|
|
|
Emmanuel Bernard, Red Hat |
|
| 304 |
|
Mobile Telephony API version 2 |
|
This JSR extends the interfaces defined in JSR253 (Mobile Telephony API) to cover additional use cases and features not covered in that JSR. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in May 2012. |
|
| Expert Group Formation |
|
Start: 2006-08-01 |
|
|
|
Brian Deuser, Motorola |
|
| 305 |
|
Annotations for Software Defect Detection |
|
This JSR will work to develop standard annotations
(such as @NonNull) that can be applied to Java programs
to assist tools that detect software defects. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in May 2012. |
|
| Expert Group Formation |
|
Start: 2006-09-12 |
|
|
|
William Pugh, Pugh, William |
|
| 306 |
|
Towards a new version of the JCP |
|
This JSR proposes a variety of changes and adjustments to the JCP. |
|
Withdrawn
|
|
This JSR was withdrawn because it is obsolete. It was replaced by two new JSRs that will develop short-term and longer-term changes to the Process Document and the JSPA. Work from JSR 306 was to be incorporated into the new JSRs as appropriate. Patrick Curran was to be the Spec Lead for these JSRs, while the Expert Group will be the current membership of both the JCP Executive Committees. |
|
| Withdrawn |
|
Effective: 2010-12-16 |
|
|
|
Patrick Curran, Oracle |
|
| 307 |
|
Network Mobility and Mobile Data API |
|
This JSR provides API's for initiating and controlling data sessions in a mobile device and providing applications control over wireless network selection. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in September 2012. |
|
| Public Review Ballot |
View results |
Start: 2009-02-17 |
End: 2009-02-23 |
|
|
Brian Deuser, Motorola |
|
| 308 |
|
Annotations on Java Types |
|
This JSR extends the Java annotation syntax to permit annotations on
any occurrence of a type. Previously, annotations could not be placed
on generic type arguments, type casts, etc. |
|
Final
|
|
|
|
Alex Buckley, Oracle |
|
Michael Ernst, Ernst, Michael |
|
| 309 |
|
Media Server Control API |
|
This Specification is a protocol agnostic API for Media Server Control. It provides a portable interface to create media rich applications with IVR, Conferencing, Speech Recognition, and similar features. |
|
Final
|
|
|
|
Marc Brandt, Hewlett-Packard |
|
Tomas Ericson, Oracle |
|
| 310 |
|
Date and Time API |
|
This JSR will provide a new and improved date and time API for Java. |
|
Final
|
|
|
|
Stephen Colebourne, Colebourne, Stephen |
|
Roger Riggs, Oracle |
|
Michael Nascimento Santos, Santos, Michael Nascimento |
|
| 312 |
|
JavaTM Business Integration 2.0 (JBI 2.0) |
|
JBI enables the creation of a Java business integration environment for the creation of Composite Applications. The JBI 2.0 JSR will augment it to address new requirements. |
|
Withdrawn
|
|
Withdrawn at the Spec Lead's request. |
|
| Withdrawn |
|
Effective: 2010-12-17 |
|
|
|
Ron Ten-Hove, Sun Microsystems, Inc. |
|
Peter Walker, Sun Microsystems, Inc. |
|
| 314 |
|
JavaServer Faces 2.0 |
|
This JSR is an update to the 1.2 version of the JavaServer Faces specification. This is the first major revision of the JavaServer Faces specification since JSR 127. |
|
Maintenance
|
|
|
|
Ed Burns, Oracle |
|
Roger Kitain, Oracle |
|
| 317 |
|
JavaTM Persistence 2.0 |
|
The Java Persistence API is the Java API for the management of persistence and object/relational mapping for Java EE and Java SE environments. |
|
Final
|
|
|
|
Linda Demichiel, Oracle |
|
| 319 |
|
Availability Management for Java |
|
This JSR will provide an API by which an availability management framework can supervise and control Java runtime units in order to achieve high availability. |
|
Withdrawn
|
|
null |
|
| Withdrawn |
|
Effective: 2021-10-19 |
|
|
|
Jens Jensen, Ericsson AB |
|
| 320 |
|
Services Framework |
|
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. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in May 2012. |
|
| Expert Group Formation |
|
Start: 2007-11-13 |
|
|
|
Roger N. Mahler, AT&T |
|
| 321 |
|
Trusted Computing API for JavaTM |
|
Develop a Trusted Computing API for JavaTM providing selected
functionality the TCG Software Stack offers to the C world, while
following the conventions of modern Java APIs. |
|
Withdrawn
|
|
null |
|
| Withdrawn |
|
Effective: 2021-10-19 |
|
|
|
Ronald Toegl, IAIK Graz University of Technology |
|
| 322 |
|
JavaTM EE Connector Architecture 1.6 |
|
The Java EE Connector Architecture 1.5 defines a standard architecture for
connecting to Enterprise Information Systems. This JSR will enhance the
existing specification with features requested by experts and community. |
|
Maintenance
|
|
|
|
Sivakumar Thyagarajan, Oracle |
|
| 323 |
|
Strong Mobility for JavaTM |
|
Strong Mobility is the movement of code, data and execution state from one location to another. This specification defines byte-code transformation to achieve Strong Mobility for Java-based programs. |
|
Rejected
|
|
This JSR was not approved by the SE/EE Executive Committee in the JSR Approval Ballot. |
|
| JSR Review Ballot Failed |
|
Start: 2008-01-22 |
|
|
|
Hiroki Suguri, Suguri, Hiroki |
|
| 324 |
|
On Screen MIDlet API for Java ME |
|
This JSR defines the API set for MIDlet activation functionality on idle screen. |
|
Rejected
|
|
This JSR was not approved by the ME Executive Committee in the JSR Approval Ballot. |
|
| Rejected |
|
Effective: 2008-04-15 |
|
|
|
Dave Kim, SK Telecom Co., Ltd. |
|
| 325 |
|
IMS Communication Enablers (ICE) |
|
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. |
|
Withdrawn
|
|
null |
|
| Withdrawn |
|
Effective: 2021-10-19 |
|
|
|
Martin Gunnang, Ericsson AB |
|
Niclas Palm, Ericsson AB |
|
| 326 |
|
Post mortem JVM Diagnostics API |
|
A standard Java API designed to support the generation and consumption of post mortem or snapshot Java diagnostic artefacts. |
|
Dormant
|
|
The Specification Lead chose to list this JSR as dormant in August 2012. |
|
| Early Draft Review |
Download page |
Start: 2009-10-29 |
End: 2009-11-28 |
|
|
Steve Poole, IBM |
|
| 327 |
|
Dynamic Contents Delivery Service API for JavaTM ME |
|
This JSR will enable Java application to interact with dynamic content delivery (DCD) client implementation in user's device. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in September 2012. |
|
|
|
Dave Kim, SK Telecom Co., Ltd. |
|
| 328 |
|
Change Management API |
|
This JSR defines an interface to Change Management Systems handling and approving Requests for Changes. |
|
Withdrawn
|
|
The JSR 328 was designed to assure a 'standard' in handling OSS(/J) change amangement and to tie it the other existing OSS/J JSRs. It was developed in close cooperation with our customer based on his requirements. Since our customer constantly diverges from the standards and since the proposal was dormant for a long time without any interest on the topic it makes no sense for our company to further pursue this proposal. |
|
| Withdrawn |
|
Effective: 2016-04-11 |
|
|
|
Christian Klaus, Ascom Deutschland GmbH |
|
| 330 |
|
Dependency Injection for Java |
|
We propose to maximize reusability, testability and maintainability of Java code by standardizing an extensible dependency injection API. |
|
Final
|
|
|
|
Rod Johnson, VMware |
|
Bob Lee, Lee, Bob |
|
| 331 |
|
Constraint Programming API |
|
This specification defines a Java runtime API for constraint programming. The CP API prescribes a set of fundamental operations used to define and solve constraint satisfaction and optimization problems. |
|
Maintenance
|
|
|
|
Jacob Feldman, Feldman, Jacob |
|
| 332 |
|
Email Client API for JavaTM ME |
|
The Email Client API (EMC) for Java ME enables Java ME applications to access Email services like sending/receiving of Emails and corresponding notifications. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in July 2013. |
|
| JSR Review Ballot |
View results |
Start: 2009-11-17 |
End: 2009-11-30 |
|
|
Gandhi Kishor Addanki, Samsung Electronics Corporation |
|
Lakshmi Narayana Thummala, Samsung Electronics Corporation |
|
| 333 |
|
Content Repository API for Java Technology 2.1 |
|
As the version 2.1 of the Content Repository for Java Technology API, the aim is to further expand and refine the specification based on feedback from the community. |
|
Dormant
|
|
The Specification Lead chose to list this JSR as dormant in December 2014. |
|
|
|
Peeter Piegaze, Adobe Systems Inc. |
|
| 334 |
|
Small Enhancements to the JavaTM Programming Language |
|
A successor to JSR 201 to enhance the Java programming language with an assortment of small changes to improve productivity. Changes must be simultaneously small in specification, implementation, and testing. |
|
Final
|
|
|
|
Joe Darcy, Oracle |
|
| 338 |
|
JavaTM Persistence 2.2 |
|
The Java Persistence API is the Java API for the management of persistence and object/relational mapping in Java EE and Java SE environments. |
|
Maintenance
|
|
|
|
Linda Demichiel, Oracle |
|
Lukas Jungmann, Oracle |
|
| 341 |
|
Expression Language 3.0 |
|
This is an update to Expression Language 2.2, currently part of JSR 245, JavaServer Page (JSP) 2.2. |
|
Final
|
|
|
|
Kinman Chung, Oracle |
|
| 343 |
|
JavaTM Message Service 2.0 |
|
This is an update to the Java Message Service API, an existing API for accessing enterprise messaging systems from Java programs. |
|
Maintenance
|
|
|
|
Nigel Deakin, Oracle |
|
| 344 |
|
JavaServerTM Faces 2.2 |
|
This JSR is an update to the 2.1 version of the JavaServer Faces specification. This is the first major revision of the JavaServer Specification since JSR 314. |
|
Final
|
|
|
|
Ed Burns, Oracle |
|
| 345 |
|
Enterprise JavaBeansTM 3.2 |
|
Enterprise JavaBeans is an architecture for the development and deployment of component-based business applications. |
|
Final
|
|
|
|
Marina Vatkina, Oracle |
|
| 347 |
|
Data Grids for the JavaTM Platform |
|
This JSR proposes an API for interacting with in-memory and disk-based distributed data grids. |
|
Withdrawn
|
|
Withdrawn at the Spec Lead's request: 'The JSR has failed to obtain sufficient interest and participation in the JCP community and has barely evolved since its inception. We are therefore requesting its withdrawal.' |
|
| Withdrawn |
|
Effective: 2015-01-06 |
|
|
|
No Current Spec Lead, No SL Company |
|
| 349 |
|
Bean Validation 1.1 |
|
Bean Validation standardizes constraint definition, declaration and validation for the Java platform. For more information on Bean Validation and how to participate, check out http://beanvalidation.org. |
|
Final
|
|
|
|
Emmanuel Bernard, Red Hat |
|
| 350 |
|
Java State Management |
|
This JSR will develop an API that applications and JavaEE containers can use to offload the responsibility of state management into third party providers with different quality of service characteristics. |
|
Rejected
|
|
This JSR was not approved to continue by the Executive Committee in the JSR Renewal Ballot. |
|
| Rejected |
|
Effective: 2015-05-12 |
|
|
|
Timothy Watson, Oracle |
|
| 351 |
|
JavaTM Identity API |
|
This JSR will develop the Identity API for the Java Platform. |
|
Withdrawn
|
|
Withdrawn at the request of the Spec Lead. |
|
| Withdrawn |
|
Effective: 2016-07-06 |
|
|
|
Ronald Monzillo, Oracle |
|
| 353 |
|
JavaTM API for JSON Processing |
|
The Java API for JSON Processing (JSON-P) JSR will develop a Java API to process (for e.g. parse, generate, transform and query) JSON. |
|
Final
|
|
|
|
Jitendra Kotamraju, Oracle |
|
| 354 |
|
Money and Currency API |
|
Provides an API for representing, transporting, and performing comprehensive calculations with Money and Currency. |
|
Maintenance
|
|
|
|
Werner Keil, Keil, Werner |
|
Otavio Santana, Santana, Otavio |
|
Anatole Tresch, Credit Suisse |
|
Anatole Tresch, Trivadis AG |
|
| 355 |
|
JCP Executive Committee Merge |
|
Since Java is One Platform this JSR will merge the two Executive Committees into one, and will reduce the total number of EC members. |
|
Final
|
|
|
|
Patrick Curran, Oracle |
|
| 357 |
|
Social Media API |
|
This specification proposes an API for accessing and providing social information networks |
|
Rejected
|
|
This JSR was not approved by the SE/EE Executive Committee in the JSR Approval Ballot. |
|
| Rejected |
|
Effective: 2012-03-20 |
|
|
|
Werner Keil, Keil, Werner |
|
Antoine Sabot-Durand, Sabot-Durand, Antoine |
|
| 358 |
|
A major revision of the Java Community Process |
|
This JSR will make a variety of changes and adjustments to the Java Community Process, revising the Process Document, the EC Standing Rules, and the JSPA. |
|
Withdrawn
|
|
At the January 2016 meeting of the JCP Executive Committee (EC) the EC was informed that Oracle Legal had advised that no changes should be made to the JSPA or to JSR licensing models while litigation is ongoing (see the public minutes for more details).
Consequently the EC decided at the March meeting to withdraw (close) JSR 358. Another JSR ('JCP.next.5') will be opened to work on changes that can be implemented by modifying only the Process Document, and we hope and expect that we will be able to pick up the more substantive changes that were being considered for JSR 358 as soon as the litigation is completed. |
|
| Withdrawn |
|
Effective: 2016-03-30 |
|
|
|
Patrick Curran, Oracle |
|
| 359 |
|
SIP Servlet 2.0 |
|
SIP Servlet API is the standard platform for implementing SIP based services. |
|
Final
|
|
|
|
Binod PG, Oracle |
|
| 361 |
|
JavaTM ME Embedded Profile |
|
Update IMP(-NG) to align with state-of-the-art features and current embedded device market requirements. |
|
Final
|
|
|
|
Volker Bauche, Oracle |
|
| 362 |
|
Portlet Specification 3.0 |
|
This update to the Portlet Specification will address progress in Java EE, client-side web, and mobile technology that has taken place since JSR286 Portlet Specification 2.0 became final in 2008. |
|
Final
|
|
|
|
Martin Nicklous, IBM |
|
| 363 |
|
Units of Measurement API |
|
This JSR specifies Java packages for modeling and working with measurement values, quantities and their corresponding units. |
|
Final
|
|
|
|
Jean-Marie Dautelle, Dautelle, Jean-Marie |
|
Werner Keil, Keil, Werner |
|
Leonardo Lima, V2COM |
|
| 364 |
|
Broadening JCP Membership |
|
This aims to broaden JCP participation by defining new membership classes, changing existing membership categories, enabling participation by the community, and ensuring the appropriate Intellectual Property commitments from JCP Members. |
|
Maintenance
|
|
|
|
Heather VanCura, Oracle |
|
| 368 |
|
JavaTM Message Service 2.1 |
|
The JMS API is an API for accessing enterprise messaging systems from Java programs. This JSR is to develop JMS 2.1, the next version of the API. |
|
Withdrawn
|
|
Withdrawn at the request of the Spec Lead. |
|
| Withdrawn |
|
Effective: 2016-11-29 |
|
|
|
Nigel Deakin, Oracle |
|
| 369 |
|
JavaTM Servlet 4.0 Specification |
|
This JSR aims to expose the latest advances in HTTP to users of JavaEE as well as providing a vehicle for continual improvement in this foundational Java EE API. |
|
Final
|
|
|
|
Ed Burns, Oracle |
|
Shing wai Chan, Oracle |
|
Xin Li, Oracle |
|
| 373 |
|
JavaTM EE Management API 2.0 |
|
This JSR is to update JSR 77 with REST interfaces and incorporate deployment as a standard part of the management interface. |
|
Withdrawn
|
|
Withdrawn at the request of the Spec Lead. |
|
| Withdrawn |
|
Effective: 2016-11-29 |
|
|
|
Martin Mares, Oracle |
|
| 375 |
|
JavaTM EE Security API |
|
The goal of this JSR is to improve the Java EE platform by ensuring the Security API aspect is useful in the modern cloud/PaaS application paradigm. |
|
Final
|
|
|
|
William Hopkins, Oracle |
|
| 377 |
|
Desktop|Embedded Application API |
|
The purpose of this specification is to standardize common behavior found in desktop & embedded applications |
|
Dormant
|
|
null |
|
| JSR Renewal Ballot 3 |
View results |
Start: 2018-06-05 |
End: 2018-06-11 |
|
|
No Current Spec Lead, No SL Company |
|
| 380 |
|
Bean Validation 2.0 |
|
This JSR aims at evolving the Bean Validation specification by leveraging Java 8 language constructs for the purposes of validation. |
|
Final
|
|
|
|
Gunnar Morling, Red Hat |
|
| 381 |
|
Visual Recognition (VisRec) Specification |
|
Java APIs for detecting, recognizing and annotating images with focus on the content of the images, facial detection, facial emotions, image tagging, specifying image classifiers and training the visual data. |
|
Final
|
|
|
|
Frank Greco, Greco, Frank |
|
Zoran Sevarac, Sevarac, Zoran |
|
| 382 |
|
Configuration API 1.0 |
|
Provide applications and microservices means to obtain configuration properties through several environment-aware sources both internal and external to the application and made available through dependency injection or lookup. |
|
Withdrawn
|
|
The Specification Leads and Expert Group agreed to withdraw the JSR and move it to the Jakarta EE spec process. |
|
| Withdrawn |
|
Effective: 2019-05-06 |
|
|
|
Emily JIANG, Eclipse Foundation, Inc |
|
Mark Struberg, Eclipse Foundation, Inc |
|
| 385 |
|
Units of Measurement API 2.0 |
|
This JSR is a major evolution of the Unit API 1.0 (JSR 363) specification. Focused on the SI System redefinition, modularity and support for Java SE 8/9 and above. |
|
Active
|
|
|
|
Jean-Marie Dautelle, Dautelle, Jean-Marie |
|
Werner Keil, Keil, Werner |
|
Otavio Santana, Santana, Otavio |
|
| 386 |
|
JavaTM SE 12 |
|
The JSR for the Java SE 12 Platform. |
|
Final
|
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, Oracle |
|
| 387 |
|
Streamline the JCP Program |
|
This JSR will make changes to the Process Document with the goals of further streamlining the organization's processes. |
|
Maintenance
|
|
|
|
Heather VanCura, Oracle |
|
| 388 |
|
JavaTM SE 13 |
|
The JSR for the Java SE 13 Platform. The Reference Implementation of this Specification is the Java Development Kit, version 13. |
|
Final
|
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, Oracle |
|
| 389 |
|
JavaTM SE 14 |
|
The JSR for the Java SE 14 Platform. The Reference Implementation of this Specification is the Java Development Kit, version 14. |
|
Final
|
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, Oracle |
|
| 390 |
|
JavaTM SE 15 |
|
The JSR for the Java SE 15 Platform. The Reference Implementation of this Specification is the Java Development Kit, version 15. |
|
Final
|
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, Oracle |
|
| 391 |
|
JavaTM SE 16 |
|
The JSR for the Java SE 16 Platform. The Reference Implementation of this Specification is the Java Development Kit, version 16. |
|
Final
|
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, Oracle |
|
| 392 |
|
JavaTM SE 17 |
|
The JSR for the Java SE 17 Platform. The Reference Implementation of this Specification is the Java Development Kit, version 17. |
|
Final
|
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, Oracle |
|
| 393 |
|
JavaTM SE 18 |
|
The JSR for the Java SE 18 Platform. The Reference Implementation of this Specification is the Java Development Kit, version 18. |
|
Final
|
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, Oracle |
|
| 394 |
|
JavaTM SE 19 |
|
The JSR for the Java SE 19 Platform. The Reference Implementation of this Specification is the Java Development Kit, version 19. |
|
Final
|
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, Oracle |
|
| 395 |
|
JavaTM SE 20 |
|
The JSR for the Java SE 20 Platform. The Reference Implementation of this Specification is the Java Development Kit, version 20. |
|
Final
|
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, Oracle |
|
| 396 |
|
JavaTM SE 21 |
|
The JSR for the Java SE 21 Platform. The Reference Implementation of this Specification is the Java Development Kit, version 21. |
|
Active
|
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, Oracle |
|
| 397 |
|
JavaTM SE 22 |
|
The JSR for the Java SE 22 Platform. The Reference Implementation of this Specification is the Java Development Kit, version 22. |
|
Active
|
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, Oracle |
|
| 398 |
|
JavaTM SE 23 |
|
The JSR for the Java SE 23 Platform. The Reference Implementation of this Specification is the Java Development Kit, version 23. |
|
Active
|
|
| Expert Group Formation |
|
Start: 2023-11-30 |
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, Oracle |
|
| 901 |
|
JavaTM Language Specification |
|
This specification includes all changes, clarifications and amendments made to the JavaTM programming language since the publication of the first edition of the language specification. |
|
Maintenance
|
|
|
|
Alex Buckley, Oracle |
|
| 913 |
|
JCP 2.0 |
|
This is the Maintenance Revision of the JCP 2.0 EC Voting rules. |
|
Maintenance
|
|
| Maintenance Draft Review |
Download page |
Start: 2001-05-08 |
End: 2001-06-11 |
|
|
Patrick Curran, Oracle |
|
| 919 |
|
JavaMailTM |
|
A description of the new APIs that are being
introduced in JavaMail. |
|
Maintenance
|
|
|
|
William Shannon, Oracle |
|
| 920 |
|
JMF 2.1.1. |
|
Maintenance Review of the JMF specification, version 2.1.1. |
|
Maintenance
|
|
| Maintenance Draft Review |
Download page |
Start: 2002-04-26 |
End: 2002-05-28 |
|
|
Babu Srinivasan, Sun Microsystems, Inc. |
|
| 922 |
|
JavaTM Communication API |
|
Maintenance version of the Java Communication API specification,version 2.0.3 |
|
Withdrawn
|
|
Withdrawn after it became clear that changes were to the implementation, not the specification. |
|
| Withdrawn |
|
Effective: 2002-12-04 |
|
|
|
Vincent Zhang, Sun Microsystems, Inc. |
|
| 923 |
|
J2SETM 1.4.2 (Mantis) Beta |
|
Descriptions of specification changes being made in version 1.4.2 ("Mantis") of the JavaTM 2 Platform, Standard Edition (J2SETM). |
|
Maintenance
|
|
| Maintenance Draft Review |
Download page |
Start: 2003-04-04 |
End: 2003-05-05 |
|
|
Danny Coward, Oracle |
|
| 926 |
|
Java 3DTM |
|
Maintenance of the Java 3D specification. |
|
Maintenance
|
|
|
|
Kevin Rushforth, Sun Microsystems, Inc. |
|
|
