Withdrawn Java^TM Specification Requests

The following Java^TM Specification Requests (JSRs) have been withdrawn from the Java Community Process^SM 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.

• JSR-000002 Boundary-Scan API
  
  Withdrawn 1999.01.09 at the request of the submitter.
  
  
• JSR-000007 Industrial Automation Extension
  
  Withdrawn 2004.10.11 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.
  
  
• JSR-000008 Open Services Gateway Specification
  
  Withdrawn 1999.11.16 because work moved to Open Services Gateway consortium (www.osgi.org) where the specification will be completed.
  
  
• JSR-000017 JAIN^TM ISUP Specification

  Withdrawn 2003.02.05. 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.

• JSR-000025 JAIN Connectivity Management
  
  Withdrawn 2000.11.21 at the request of the submitter.
  
  
• JSR-000026 UML/EJB Mapping Specification
  
  Withdrawn 2004.03.29 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.
  
  
• JSR-000027 Java Cryptography Extension 1.3
  
  Withdrawn 1999.11.05 before work began because it describes a cryptographic system and/or a crytpographic framework whose implementation would be subject to U.S. Export Licensing requirements.
  
  
• JSR-000029 JAIN^TM MAP Specification
  
  Withdrawn 2003.05.30 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.
  
  
• JSR-000033 InfoBus 2.0 Specification
  
  Withdrawn 1999.11.08 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.
  
  
• JSR-000039 Java^TM Servlet and JSP Performance Benchmark
  
  Withdrawn 2001.10.02 at the request of the submitter.
  
  
• JSR-000042 Travel Industry Reservation Booking Foundation API Specification
  
  Withdrawn 2000.06.13 at the request of the submitter. Community support was not sufficient to form an expert group.
  
  
• JSR-000044 Braille API Specification
  
  Withdrawn 2000.11.21 at the request of the submitter. Community support was not sufficient to support an Expert Group.
  
  
• JSR-000061 Phonelets API Specification

  Withdrawn 2004.04.09 at the request of the Spec Lead after 4 years with no Expert Group.
  
  

• JSR-000064 Financial Services Party Component
  
  Withdrawn 2000.08.30 at the request of the submitter. XML party components for this functionality are being developed under the Customer Profile Exchange (CPex).
  
  
• JSR-000065 Concise Object-Array Literals
  
  Withdrawn 2003.07.25 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.
  
  
• JSR-000070 IIOP Protocol Adapter for JMX^TM Specification

  Withdrawn 2003.10.23 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.
  
  

• JSR-000071 JMX-TMN Specification
  
  
• JSR-000074 Public Key Crypotography Standards (PKCS) 1.0

  Withdrawn 2004.01.14 as the main goals of this JSR have now been achieved and delivered through J2SE and other JCP specifications.
  
  

• JSR-000081 JAIN^TM H323

  Due to the general absence of interest in the Community, the Specification Lead decided to withdraw the JSR from development.

• JSR-000083 Multiarray package

  Withdrawn 2005.09.06. 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.

• JSR-000084 Floating Point Extensions

  Withdrawn 2002.03.01. Due to the general absence of interest in the community, the Specification lead withdrew the JSR.

• JSR-000092 Localizable Text

  Withdrawn 2005.02.08. The Spec Lead provided the following explanation: "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."

• JSR-000096 Java^TM Daemons

  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 Commu nity Process.

• JSR-000103 JAIN^TM User Interaction API

  Withdrawn 2003.03.21 following decisions at the November 2002 JAIN meeting in Austin.

• JSR-000108 Units Specification

  Withdrawn 2004.07.23 after the Spec Lead left the JCP and none of the Expert Group took over as Spec Lead.




• JSR-000111 Java^TM Services Framework

  Withdrawn 2003.08.19 with the agreement of the Expert Group.

• JSR-000117 J2EE^TM APIs for Continuous Availability

  Withdrawn 2003.08.25 with the agreement of the Expert Group.

• JSR-000119 JAIN^TM SPA Integrity Management and Event Notification API

  With agreement from the Expert Group, the Spec Lead decided to withdrawn this JSR on 2003.02.24 following decisions at the November 2002 JAIN meeting in Austin.

• JSR-000123 JAIN^TM Presence and Availability Management (PAM) API

  Withdrawn 2004.03.19 after unable to find anyone 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 specification.

• JSR-000125 JAIN^TM SIP Lite

  Withdrawn 2006.03.14 after no one on the Expert Group offered to take over the Spec Lead role. "Because of the resourcing issues, Nortel will like to withdraw from the JSR125. We are unable to provide the RI and the TCK, but believe that this is the right approach for a Proxy and small footprint SIP servers/Clients."

• JSR-000126 Distributed Page Assembly

  Withdrawn 2003.11.10. 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.

• JSR-000132 JAIN^TM OAM API Specification v2.0

  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.

• JSR-000134 Java^TM Game Profile

  Withdrawn 2003.07.09. 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.

• JSR-000136 Java^TM Technology for Service Providers

  Withdrawn 2004.03.19 as community support was not sufficient to support an Expert Group.

• JSR-000137 JAIN^TM 3G Map Specification

  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 on 2003.03.04.

• JSR-000140 Service Location Protocol API for Java

  Withdrawn 2004.10.05. 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.

• JSR-000145 JAIN^TM SPA Cpmmon API

  Withdrawn 2003.02.14. Read the Spec Lead's explanation of the withdrawal here.

• JSR-000146 WBEM Services: JMX Provider Protocol Adapter

  Withdrawn 2003.07.14 by the Spec Lead. After a year and a half of no progress, the Spec Lead suggested withdrawing the JSR and the Expert Group did not object.

• JSR-000148 3DMedia Utilities

  After over a year of no development, the Spec Lead suggested withdrawing the JSR and the Expert Group did not object.

• JSR-000149 Work Area Service for J2EE^TM

  Withdrawn 2005.10.26: "JSR-149 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 withdrew the JSR once no one in the Expert Group agreed to take over the Spec Lead role.

• JSR-000150 Internationalization Service for J2EE^TM

  Withdrawn 2008.10.30: "JSR-150 has been idle for several years now and the existing draft has not kept pace with changes in J2EE. The Spec Lead wishes to withdraw the JSR. None of the EG members has objected."

• JSR-000159 Java^TM Process Component API (JPC)

  Withdrawn 2003.05.05 by the JSR 159 Spec Lead with assent from the Expert Group.

• JSR-000162 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.

• JSR-000167 Java^TM Portlet Specification

  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.

• JSR-000183 Web Services Message Security APIs

  Withdrawn on 2008.08.05: 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 is being withdrawn.

• JSR-000189 Java^TM 3D API 1.4

  Withdrawn on 2005.11.08: 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 nearly three years ago, 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.

  The Java 3D API is now a community source project on java.net, where all new development has happened over the past 18 months. We are actively developing the 1.4 API release with help from the Java 3D community on java.net. This release is a much more modest undertaking than was originally planned, and all new API changes are being designed with public input. As such we are closing this JSR, and are doing Java 3D 1.4 as a maintenance release under the JCP.

• JSR-000191 JAIN^TM GCCS API

  Withdrawn on 2003.03.21 following agreement with the Expert Group after the decisions at the November 2002 JAIN meeting in Austin.

• JSR-000192 JAIN^TM Service Creation Environment - Java^TM PART

  Withdrawn on 2004.09.22 by the JSR 192 Spec Lead: "There has 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. We have now decided not to go ahead with this activity and hence you are request to mark this JSR 192 as WITHDRAWN."

• JSR-000193 Client Side Containers (CSC)

  Having noticed the many questions/concerns about this specification proposal, the submitter decided to withdraw the request.

• JSR-000194 JAIN^TM ULS API

  With agreement from his Expert Group, the Spec Lead decided to withdrawn this JSR on 2003.02.21 following decisions at the November 2002 JAIN meeting in Austin.

• JSR-000237 Work Manager for Application Servers

  Withdrawn 2008.06.18. The Spec Leads provided this information: "JSR 237 has been merged with JSR 236, providing a single, consistent specification for Java EE concurrency."

• JSR-000922 Java^TM Communication API

  Withdrawn 2002.12.04 after it became clear that changes were to the implementation, not the specification.