About JCP
Get Involved
Community Resources
Community News
FAQ
Contact Us
|
|
JSRs: Java Specification Requests
JSRs by Query - java persistence - 250 found
| 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 |
 |
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 926 |
|
Java 3DTM |
|
Maintenance of the Java 3D specification. |
|
Maintenance
|
|
|
|
Kevin Rushforth, Sun Microsystems, Inc. |
|
| 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 |
|
| 28 |
|
Java SASL Specification |
|
This specification defines a SASL client and server API in the JavaTM programming language. |
|
Final
|
|
|
|
Rosanna Lee, Sun Microsystems, Inc. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 386 |
|
JavaTM SE 12 |
|
The JSR for the Java SE 12 Platform. |
|
Final
|
|
|
|
Iris Clark, Oracle |
|
Brian Goetz, 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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. |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| Rejected |
|
Effective: 2008-01-22 |
|
|
|
Hiroki Suguri, Suguri, Hiroki |
|
| 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. |
|
| 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 |
|
| 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. |
|
| 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. |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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. |
|
| 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. |
|
| 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) |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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. |
|
| 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 |
|
| 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) |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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. |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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. |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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. |
|
| 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 |
|
| 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. |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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. |
|
| 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. |
|
| 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 |
|
| 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) |
|
| 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 |
|
|
