About JCP
Get Involved
Community Resources
Community News
FAQ
Contact Us
|
|
JSR Review (0 JSRs) |
Early Draft Review (0 JSRs) |
Public Review (0 JSRs) |
Proposed Final Draft (0 JSRs) |
Final Release (271 JSRs) |
Maintenance Review (0 JSRs) |
Active (10 JSRs) |
Inactive (0 JSRs) |
Dormant (26 JSRs) |
Withdrawn (102 JSRs) |
Rejected (14 JSRs)
The following JavaTM Specification Requests (JSRs) have been withdrawn from the Java Community ProcessSM Program for the reasons stated.
PLEASE NOTE: These JSRs represent proposed specifications that were either not started or not completed. Those that were started, but not completed, are usually being completed elsewhere. See below for details. Note that a Java Specification Request may have been Accepted from the JSR Approval Ballot but withdrawn later.
| 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 |
|
| 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. |
|
| 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 |
|
| 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. |
|
| 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. |
|
| 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 |
|
| 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) |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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) |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
|
