JSRs by Platform JSRs by Technology JSRs by Stage JSRs by Committee List of All JSRs
About JCP
Get Involved
Community Resources
Community News
FAQ Contact Us
About JCP
Get Involved
Community Resources
Community News
FAQ Contact Us
Description: The Real-Time Specification for Java extends the JavaTM platform to support both current practice and advanced real-time systems application programming.
Spec Lead: Peter Dibble, TimeSys Corporation
![[image]](http://mowser.com/img?url=http%3A%2F%2Fjcp.org%2Fimages%2Fjsr%2Fyel-horiz-bar.gif)
Description: 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.
Spec Lead: Copra Dau-esk, Trangadst Shipping Services
Spec Lead: Neil Jacobson, Xilinx
Description: 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.
Spec Lead: Eamonn McManus, Oracle
Description: ECperf is an EJBTM performance workload that is real-world, scalable and captures the essence of why component models exist.
Spec Lead: Shanti Subramanyam, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Rajiv Mordani, Oracle
Description: This unified Java Print API will be based on a print model that meets the requirements of the current Java 2 Print API and JiniTM Printing.
Spec Lead: Robert Herriot, Xerox
Description: The Industrial Automation specification will result in an industry standard for industrial automation that is based on the JavaTM and JiniTM technologies.
Spec Lead: Bruce Khavar, Cyberonix
Spec Lead: Tamsin Vantress, Cyberonix
Description: This JSR was going to develop the Open Services Gateway (OSG) Specification and describe an extensible Service Gateway.
Spec Lead: Xander Bighorn, Trangadst Shipping Services
Spec Lead: Robert Mines, Sun Microsystems, Inc.
Description: The Federated Management Architecture (FMA) specifies a storage management platform that will allow vendors to construct storage management applications from standard and custom components.
Spec Lead: William Connor, Phd., Sun Microsystems, Inc.
Description: A simple API allowing programs to manipulate user preference data and configuration data.
Spec Lead: Joshua Bloch, Sun Microsystems, Inc.
Description: JAINTM TCAP JSR is a proposed Java specification for the TCAP layer of the Signaling System 7 (SS7) stack.
Spec Lead: Phelim O'Doherty, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Craig Russell, Sun Microsystems, Inc.
Description: This primarily adds floating point arithmetic to the BigDecimal class, allowing the use of decimal numbers for general-purpose arithmetic without the problems resulting from conversions to and from another type.
Spec Lead: Joe Darcy, Oracle
Description: Extending the JavaTM programming language with generic types (aka parameterized types).
Spec Lead: Alex Buckley, Oracle
Description: Image I/O supports image reader and writer plug-ins for sampled image formats. The API provides for exposure and preservation of metadata as well as pixel data.
Spec Lead: Phil Race, Sun Microsystems, Inc.
Description: The J2EETM Connector architecture defines a standard architecture for integrating JavaTM applications with existing back-end Enterprise Information systems.
Spec Lead: Binod PG, Sun Microsystems, Inc.
Description: Requirements for a Standard Java API for ISDN User Part (ISUP), an SS7 protocol.
Spec Lead: Vijaya Venkatachalam, Ulticom
Description: JAINTM Operations, Administration, and Maintenance (OAM) defines a standard API for provisioning and managing protocol interfaces in the Telecommunications and Internet Industry.
Spec Lead: Doug Tait, Sun Microsystems, Inc.
Description: 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.
Spec Lead: 
Linda DeMichiel, Oracle
Linda DeMichiel, OracleDescription: Orthogonal persistence for the JavaTM platform (OPJ) would have provided persistence for the full computational model specified by the JavaTM Language Specification (JLS).
Spec Lead: Mick Jordan, Oracle
Description: 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.
Spec Lead: John-Luc Bakker, Telcordia Technologies, Inc.
Description: Descriptions of all interfaces, classes, exceptions and requirements to develop portable telecommunication services and application frameworks so that services once developed will run on any JAINTM SLEE-compliant execution environment.
Spec Lead: David Ferry, Open Cloud Limited
Description: This work will specify the JAINTM API through which access to protocol stacks that support the Media Gateway Control Protocol (RFC 2705) may be achieved.
Spec Lead: John-Luc Bakker, Telcordia Technologies, Inc.
Description: This allows software developers to rapidly develop external Service Provider-type applications to securely access, discover and agree other APIs, which use abstract primitives that hide the heterogeneity of underlying networks.
Spec Lead: Anders Lundqvist, Incomit AB
Description: The JSR is to define the Java APIs for a Connectivity Management API specification.
Spec Lead: Rob Goedman, Sun Microsystems, Inc.
Description: This document describes a standard mapping between the Enterprise JavaBeansTM architecture and the Unified Modeling Language.
Spec Lead: Andy Dean, IBM
Description: This Specification would have enhanced the JavaTM Cryptography Extension 1.2 and made it exportable.
Spec Lead: Sharon Liu, Sun Microsystems, Inc.
Spec Lead: Jan Luehe, Sun Microsystems, Inc.
Description: This specification defines a SASL client and server API in the JavaTM programming language.
Spec Lead: Rosanna Lee, Sun Microsystems, Inc.
Description: 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.
Spec Lead: S?ren Torstensson, Ericsson Inc.
Description: This specification will define a standard platform configuration of the JavaTM 2 platform, Micro Edition (J2METM) for small, resource-limited, connected devices.
Spec Lead: Antero Taivalsaari, Sun Microsystems, Inc.
Description: A facility for compiling an XML schema into one or more JavaTM classes which can parse, generate, and validate documents that follow the schema.
Spec Lead: Joe Fialli, Oracle
Spec Lead: Sekhar Vajjhala, Sun Microsystems, Inc.
Description: The JAINTM SIP API specification provides a standard portable interface to share information between SIP Clients and SIP Servers, providing call control elements enabling converged-network applications.
Spec Lead: Phelim O'Doherty, Oracle
Spec Lead: Mudumbai Ranganathan, NIST
Description: 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.
Spec Lead: Mark Colan, Lotus Development Corporation
Description: Revision of the JavaTM Advanced Imaging API specification to version 1.1. Java Advanced Imaging supports sophisticated image processing in Java 2.
Spec Lead: John Zimmerman, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Shankar Allimatti, Mahindra British Telecom Ltd.
Description: The Connected Device Configuration (CDC) provides the basis of the JavaTM 2 platform, Micro Edition for devices that have a sufficient 32-bit microprocessor and ample memory.
Spec Lead: Jon Courtney, Sun Microsystems, Inc.
Jon Courtney, Sun Microsystems, Inc.Description: This specification will define a profile that will extend and enhance the "J2METM Connected, Limited Device Configuration" (JSR-000030), enabling application development for mobile information appliances and voice communication devices.
Spec Lead: Brian Deuser, Motorola
Description: 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.
Spec Lead: Paul Lovvik, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Ruslan Belkin, America Online (AOL)
Description: The Java Metadata Interface specification will address the need for a pure Java metadata framework API that supports the creation, storage, retrieval, and interchange of metadata.
Spec Lead: Ravi Dirckze, Unisys
Description: A new keyword allowing programmers to include assertions describing intended program behavior, which can be checked as programs execute to detect bugs.
Spec Lead: Joshua Bloch, Sun Microsystems, Inc.
Description: 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).
Submitter: Sherry Shavor, IBM
Description: JTAPI 1.4 extends and enhances the current Java Telephony specification.
Spec Lead: Jeff Peck, Enterprise Computer Telephony Forum (ECTF)
Spec Lead: Richard J. Pennenga, Enterprise Computer Telephony Forum (ECTF)
Description: 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.
Spec Lead: Ramon Cabello, O.N.C.E.
Description: This specification establishes standardized tools for correlating JavaTM virtual machine byte code to source code of languages other than the JavaTM programming language.
Spec Lead: Robert Field, Oracle
Description: The Foundation Profile is a set of APIs meant for applications running on small devices that have some type of network connection.
Spec Lead: Jon Courtney, Sun Microsystems, Inc.
Jon Courtney, Sun Microsystems, Inc.Description: Define standard logging APIs for the error and trace logging.
Spec Lead: Danny Coward, Oracle
Description: 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.
Spec Lead: Carl Chan, WBEM Solutions, Inc
Spec Lead: Jim Davis, WBEM Solutions, Inc
Description: 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.
Spec Lead: Hiroaki Hashimukai, Yamatake Corporation
Description: The Distributed Real-Time Specification for Java extends RMI in the Real-Time Specification for Java, to provide support for predictability of end-to-end timeliness of trans-node activities.
Spec Lead: James J. Hunt, Aicas GmbH
Description: APIs for scalable I/O, fast buffered binary and character I/O, regular expressions, charset conversion, and an improved filesystem interface.
Spec Lead: Mark Reinhold, Sun Microsystems, Inc.
Mark Reinhold, Sun Microsystems, Inc.Description: A standard tag library for JSPTM pages.
Spec Lead: Jan Luehe, Sun Microsystems, Inc.
Spec Lead: Eduardo Pelegri-Llopart, Sun Microsystems, Inc.
Description: The next versions of the JavaTM Servlet and JavaServer PagesTM (JSP) specifications.
Spec Lead: Eduardo Pelegri-Llopart, Sun Microsystems, Inc.
Description: The proposed specification will update the JDBCTM specification to reflect changes in the SQL specification and JavaTM platform.
Spec Lead: Lance Andersen, Oracle
Description: The Certification Path API provides a set of provider-based APIs for creating, building, and verifying certification paths (also known as "certificate chains").
Spec Lead: Sean Mullan, Sun Microsystems, Inc.
Description: A specification of protocols and APIs that will enable JavaTM applications to be deployed on the Web.
Spec Lead: Andy Herrick, Oracle
Description: JSR 57 provides streams to convert graphs of JavaBeansTM architecture to and from version resilient file formats (typically XML documents).
Spec Lead: Mark Davidson, Sun Microsystems, Inc.
Description: Defines the JavaTM 2 Platform, Enterprise Edition, version 1.3.
Spec Lead: Bill Shannon, Sun Microsystems, Inc.
Bill Shannon, Sun Microsystems, Inc.Description: Define the major features of the J2SETM "Merlin" release (J2SE 1.4).
Spec Lead: Danny Coward, Oracle
Description: The goal is to develop a set of Java APIs for programmable controllers in the building automation industry.
Spec Lead: Brian Frank, Tridium, Inc
Description: Phonelets provide developers with a simple API to package, deploy and run Computer Telephony Integration (CTI) applications in a resource and security controlled environment.
Spec Lead: Marc Petit-Huguenin, 8x8
Description: The J2METM Personal Profile provides the J2ME environment for those devices with a need for a high degree of Internet connectivity and web fidelity.
Spec Lead: Jon Courtney, Sun Microsystems, Inc.
Jon Courtney, Sun Microsystems, Inc.Description: The proposed specification will define a set of implementation independent portable APIs supporting XML Processing.
Spec Lead: Rajiv Mordani, Oracle
Description: This JSR is a proposal to define an Enterprise Java BeanTM (EJBTM) component interface for party information as required by the financial services domain.
Submitter: William Senn, IBM
Description: A minor extension to the JavaTM programming language that will support a concise notation for automatically-boxing object-array literals.
Spec Lead: Gilad Bracha, Sun Microsystems, Inc.
Description: The J2METM RMI Optional Package (RMI OP) provides JavaTM platform to Java platform remote method invocation for Java devices and interoperates with J2SETM RMI.
Spec Lead: Mark Hodapp, Sun Microsystems, Inc.
Description: JAXM provides an API for packaging and transporting business transactions using on-the-wire protocols being defined by ebXML.org, Oasis, W3C and IETF.
Spec Lead: V B Kumar Jayanti, Sun Microsystems, Inc.
Description: This specification will define the next major revision of the JavaTM 2 platform, Micro Edition.
Spec Lead: Roger Riggs, Oracle
Description: 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.
Spec Lead: John D. Poole, Hyperion Solutions Corporation
Description: This specification will establish an IIOP based adapter for the JMXTM specification to allow CORBA clients access JMX agents.
Spec Lead: Damian McGrath, Progress Software
Description: 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.
Spec Lead: Aline Ellul, Evidian
Description: 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.
Spec Lead: Seema Malkani, Sun Microsystems, Inc.
Description: This JSR addresses the need for a data mining API aligned with existing, evolving data mining standards efforts.
Spec Lead: Mark F. Hornick, Oracle
Mark F. Hornick, OracleDescription: 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).
Spec Lead: Seema Malkani, Sun Microsystems, Inc.
Description: This JSR produces two separate optional packages for features commonly found on PDAs and other J2ME mobile devices: one for accessing PIM data and one for accessing file systems.
Spec Lead: Tom Chavez, PalmSource, Inc.
Spec Lead: Ken Walker, IBM
Description: Define a high-level API for network security in JavaTM 2 Standard Edition RMI, covering basic security mechanisms: authentication (including delegation), confidentiality, and integrity.
Spec Lead: Bob Scheifler, Sun Microsystems, Inc.
Description: The JavaTM 2 Platform, Enterprise Edition Management Specification will provide server vendors and tool vendors with a standard model for managing the J2EE Platform.
Spec Lead: Hans Hrasna, Oracle
Description: Provide a general framework in JavaTM 2 Standard Edition RMI for customizing remote invocation behavior.
Spec Lead: Ann Wollrath, Sun Microsystems, Inc.
Description: This work will specify the JAINTM API through which access to protocol stacks that support the MEGACO/H.248 protocol may be achieved.
Spec Lead: Vikas Bajaj, Hughes Software Systems
Description: This specification provides a JavaTM API for communicating with devices attached via the Universal Serial Bus (USB). It allows Java applications to discover, read, write, and manage USB devices.
Spec Lead: Boyd Dimmock, IBM
Description: H.323 defines a system for moving real-time bi-directional multimedia (video, voice, data, fax, etc.) across packet-based networks.
Spec Lead: Orit Levin, RADvision
Description: Bluetooth is an important emerging standard for wireless integration of small devices. The specification standardizes a set of Java APIs to allow Java-enabled devices to integrate into a Bluetooth environment.
Spec Lead: Angus Huang, Aplix Corporation
Description: This JSR proposes a package implementing true rectangular multidimensional arrays for the JavaTM platform.
Spec Lead: Jose E. Moreira, IBM
Description: This JSR proposes extensions to the JavaTM Programming Language and Java Virtual Machine that support more efficient execution of floating point code.
Spec Lead: Marc Snir, IBM
Description: Define an API for managing and accessing a rules-based authorization and audit trail service.
Spec Lead: Hal Lockhart, Entegrity Solutions
Description: Enterprise Media Beans provide a framework to integrate rich media data (i.e. audio, video, or image) into applications based on EJBTM Entity Beans within the J2EETM application development model.
Submitter: Lou Raymundo, Watchmark Corporation
Description: This specification defines a set of objects and service interfaces to support the deployment and operation of autonomous communicative agents.
Spec Lead: Francis G. McCabe, Fujitsu Limited
Description: This specification provides a complete description of the APIs required by the J2EE platform to enable development of platform-independent deployment tools.
Spec Lead: Jerome Dochez, Oracle
Description: Provide an API that allows telecom management applications to be developed and integrated with Java-enabled Service Activation systems.
Spec Lead: Andreas Ebbert-Karroum, codecentric AG
Description: Provide an API that allows telecom management applications to be developed and integrated with Java-enabled Quality of Service systems.
Spec Lead: Ashutosh Sharma, Wipro Technologies
Description: The OSS Trouble Ticket API will provide interfaces for creating, querying, updating, and deleting trouble tickets (trouble reports).
Spec Lead: Roman Schlegel, Frox Communication
Description: Localizable Text is the infrastructure necessary to translate language-neutral information (in an object) from anywhere in a distributed network.
Spec Lead: Debasish Banerjee, IBM
Description: 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.
Spec Lead: Paul Sterk, Sun Microsystems, Inc.
Description: This specification defines a Java runtime API for rule engines.
Spec Lead: Daniel Selman, ILOG
Description: The Activity Service supports flexible ways of composing an application using transactions, and can enable the application to possess some or all ACID properties.
Spec Lead: Ian Robinson, IBM
Description: 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.
Spec Lead: Thomas Kopp, Dialogika GMBH
Description: A major update to the JavaHelp 1.0 Specification, including enhancements to merging, multi-topic printing, improved secondary window and popup usage, JFC ToolTip HelpSet support, HelpSet presentation controls and additional Navigators.
Spec Lead: Roger Brinkley, Oracle
Description: The JAIN User Location and Status 1.0 API is the Java specification of the Parlay Mobility 2.1 API.
Spec Lead: Ulf Lange, Siemens AG
Description: This is the major revision of the Java Specification Participation Agreement.
Spec Lead: Jonathan Nimer, Sun Microsystems, Inc.
Description: 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.
Spec Lead: John-Luc Bakker, Telcordia Technologies, Inc.
Description: Java APIs to support emerging industry XML based RPC standards.
Spec Lead: Roberto Chinnici, Oracle
Description: JDOM is a way to represent an XML document for easy and efficient reading, manipulation, and writing.
Spec Lead: Jason Hunter, Hunter, Jason
Description: This was intended to allow software developers to rapidly develop external Service Provider-type applications using abstract primitives that hide the heterogeneity of underlying networks.
Spec Lead: Judith Russell, AePONA
Description: This defines a standard set of APIs and a protocol for a "Trust Service", minimizing the complexity of applications using XML Signature.
Submitter: Anthony Nadalin, IBM
Description: This defines and incorporates a standard set of high-level implementation-independent APIs for XML digital signatures services. The XML Digital Signature specification is defined by the W3C.
Spec Lead: Sean Mullan, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Bruce Rich, IBM
Description: Specifies API and semantics for temporary, in memory caching of Java objects, including object creation, shared access, spooling, invalidation, and consistency across JVM's.
Spec Lead: Yannis Cosmadopoulos, Oracle
Spec Lead: Gregory Luck, Luck, Gregory Robert
Spec Lead: Cameron Purdy, Oracle
Description: 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.
Spec Lead: Steven Emmerson, University Corporation for Atmospheric Research (UCAR)
Description: This specification defines the programming model and runtime architecture for implementing web services in Java.
Spec Lead: Jitendra Kotamraju, Oracle
Description: 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.
Spec Lead: Graham C Turrell, IBM
Description: 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.
Spec Lead: Berin Loritsch, Loritsch, Berin
Description: 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.
Spec Lead: Binod PG, Sun Microsystems, Inc.
Description: This JSR extends the work of the 1.0 JavaTM Speech API, specifying a cross-platform interface to support speech recognizers and synthesizers.
Spec Lead: Charles Hemphill, EverSpeech, Inc.
Description: JavaTM API providing implementations of the JDBC Rowset interface.
Spec Lead: Lance Andersen, Oracle
Description: This JSR seeks to define a contract between containers and authorization service providers that will result in the implementation of providers for use by containers.
Spec Lead: Ron Monzillo, Oracle
Description: The SIP Servlet API defines a high-level extension API for SIP servers. It enables SIP applications to be deployed and managed based on the servlet model.
Spec Lead: Anders Kristensen, Dynamicsoft, Inc
Description: This specification defines the programming model and runtime support for implementing J2EE applications requiring continuous availability.
Spec Lead: Max Mortazavi, Sun Microsystems, Inc.
Description: This specification will define a profile that will extend and enhance the "J2METM Mobile Information Device Profile" (JSR-000037).
Spec Lead: Paul Su, Aplix Corporation
Description: The API was intended to allow software developers to rapidly develop external Service Provider-type applications to maintain service intergrity and receive generic service-related events.
Spec Lead: Anders Lundqvist, Incomit AB
Description: This defines a set of optional APIs which provides standard access to wireless communication resources, designed to run on J2ME configurations and to enhance J2ME profiles with unique functionality.
Spec Lead: Marquart C Franz, Siemens AG
Description: An API for initiating and controlling computations isolated from each other to varying degrees. Some API semantics are similar to those of ThreadGroup.
Spec Lead: Krzysztof Palacz, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Farooq M Anjum, Telcordia Technologies, Inc.
Description: JAINTM SPA Presence and Availability Management API will provide Java APIs to disseminate and manage presence information securely across heterogeneous networks and applications.
Spec Lead: Jorge Lobo, Teltier Technologies
Description: This JSR aims to define Java standard which partitions server applications that provision client applications.
Spec Lead: Danny Coward, Oracle
Description: The JAINTM SIP Lite API defines a high level API to the SIP stack to allow for the rapid development of applications.
Spec Lead: David Tweedie, Nortel
Description: This specification defines a standard application model and architecture for distributed page assembly within the J2EE framework.
Spec Lead: Rajesh Agarwalla, IBM
Spec Lead: Steve Ims, IBM
Description: This specification defines an architecture and APIs which simplify the creation and maintenance of Java Server application GUIs.
Spec Lead: Edward Burns, Oracle
Spec Lead: Craig R. McClanahan, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Olga Peschansky, Oracle
Description: The J2METM Personal Basis Profile provides a J2ME application environment for network-connected devices supporting a basic level of graphical presentation.
Spec Lead: Jon Courtney, Sun Microsystems, Inc.
Jon Courtney, Sun Microsystems, Inc.Description: 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.
Spec Lead: Tulika Pradhan, Infozech Software Ltd.
Description: ECperf 1.1 is a maintenance release of ECperf 1.0. The ECperf 1.1 Expert Group will also be responsible for evaluating and accepting ECperf 1.0 results submitted.
Spec Lead: Shanti Subramanyam, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Phelim O'Doherty, Sun Microsystems, Inc.
Description: The proposed specification describes the semantics of threads, locks, volatile variables and data races. This includes what has been referred to as the Java memory model.
Spec Lead: William Pugh, Pugh, William
Description: Defines a Java 2 Micro Edition Profile for the purposes of game development targeting high-end consumer game devices and desktops.
Spec Lead: Bartley Calder, Sun Microsystems, Inc.
Description: This specifies a small-footprint multimedia API for J2METM, allowing simple, easy access and control of basic audio and multimedia resources while also addressing scalability and support of more sophisticated features.
Spec Lead: Lakshmi Dontamsetti, Aplix Corporation
Description: 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.
Spec Lead: Mauricio Arango, Sun Microsystems, Inc.
Description: This JSR is to develop the JAINTM 3G MAP APIs which will enable mobile applications in the 3G domain to talk to each other.
Spec Lead: Sanjiv Kapur, Hughes Software Systems
Description: Specifies standard APIs for performance metric instrumentation of Java programs.
Spec Lead: Bruce Irvin, Oracle
Description: This specification will define a revised version of the J2METM Connected, Limited Device Configuration (CLDC).
Spec Lead: Roger Riggs, Oracle
Description: This JSR is to standardize the Service Location Protocol Application Programmer Interface for Java as described in RFC 2614.
Spec Lead: Nick Briers, The SCO Group
Description: The IETF protocol SDP specifies messages that describe multi-media sessions and are included within other protocol messages as payload. The API will enable users to manipulate SDP messages.
Spec Lead: Kelvin R Porter, Cisco Systems
Description: The OSS Inventory API defines J2EE based interfaces between inventory repositories and other OSS components.
Spec Lead: Pierre Gauthier, Oracle
Pierre Gauthier, OracleDescription: JavaDesk provides a standard desktop API across platforms using an MVC model. Applications can control and enhance the desktop using the JavaDesk API.
Spec Lead: Rich Isaac, Bay Equities, Inc.
Description: 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.
Spec Lead: Vincent Perrot, Sun Microsystems, Inc.
Vincent Perrot, Sun Microsystems, Inc.Description: This JSR will specify the set of APIs common across the JAIN SPA JSRs. This will provide consistency by reducing duplication of common interfaces and classes among these JSRs.
Spec Lead: Gary Bruce, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Chris Seibel, Sun Microsystems, Inc.
Description: Workspace Versioning and Configuration Management provides client support for creating and manipulating sets of version-controlled files and web resources.
Spec Lead: Geoffrey Clemm, IBM
Description: The 3D Media Utilities API specifies classes and interfaces for 3D vector operations and volumetric imaging.
Spec Lead: Brian Burkhalter, Sun Microsystems, Inc.
Spec Lead: Kevin Rushforth, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Heath Thomann, IBM
Description: The Internationalization Service enables distributed localization within Enterprise Java applications by transparently propagating and managing localization information within relevant J2EE application components.
Spec Lead: Charles Hornig, IBM
Description: This JSR is to develop J2EE 1.4, the next release of the Java 2 Platform, Enterprise Edition.
Spec Lead: Mark Hapner, Sun Microsystems, Inc.
Spec Lead: Bill Shannon, Sun Microsystems, Inc.
Bill Shannon, Sun Microsystems, Inc.Description: Next revision of the JavaServer PagesTM specification.
Spec Lead: Eduardo Pelegri-Llopart, Sun Microsystems, Inc.
Spec Lead: Mark Roth, Sun Microsystems, Inc.
Description: The Enterprise JavaBeans 2.1 specification adds to the EJB architecture support for web services, extensions to message-driven beans, enhancements to EJB QL, and a container-managed timer service.
Spec Lead: Linda DeMichiel, Oracle
Linda DeMichiel, OracleDescription: This specification will build on servlet specification version 2.3 by enhancing existing features and adding new facilities of a reasonably small nature.
Spec Lead: Rajiv Mordani, Oracle
Description: To provide a set of APIs, exchange patterns & implementation to securely (integrity and confidentiality) exchange assertions between web services based on OASIS SAML.
Spec Lead: Sandeep Kumar, Cisco Systems
Spec Lead: Krishna Sankar, Cisco Systems
Description: 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.
Spec Lead: Jonathan Halliday, RedHat
Description: 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.
Spec Lead: Himagiri Mukkamala, Sybase
Description: TheJavaTM Stream Assembly API specifies classes and interfaces for the creation, management, and processing of broadcast and interactive stream multiplexes.
Spec Lead: Gerard Fernando, Sun Microsystems, Inc.
Description: JPC would have defined a loosely coupled, event based process component model that would simplify the development of composable, customizable services.
Spec Lead: Mark Hapner, Sun Microsystems, Inc.
Description: This API extends the JMX 1.2 API to provide remote access to JMX MBean servers.
Spec Lead: Eamonn McManus, Oracle
Spec Lead: Simon Vienot, Sun Microsystems, Inc.
Description: The JAINTM ENUM API Specification defines a standard, portable application programming interface to query and provision E.164 telephone numbers and their service-specific Uniform Resource Identifiers (URI).
Spec Lead: Christopher John, NetNumber, Inc.
Description: 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.
Spec Lead: Stefan Hepper, IBM
Stefan Hepper, IBMDescription: A mechanism and APIs for extracting time and space profiling information from a running JavaTM virtual machine.
Spec Lead: Robert Field, Oracle
Description: SIMPLE Presence provides a standard portable and secure interface to manipulate presence information between a SIMPLE client (watcher) and a presence server (presence agent).
Spec Lead: Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory
Description: SIMPLE Instant Messaging provides a standard portable and secure interface to exchange messages between SIMPLE clients. SIMPLE is an extension of SIP to support presence and instant messaging.
Spec Lead: Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory
Description: The JSR proposes a set of medium-level utilities that provide functionality commonly needed in concurrent programs.
Spec Lead: Doug Lea, Lea, Doug
Description: This specification would have defined a set of APIs for Portal computing addressing the areas of aggregation, personalization, presentation and security.
Spec Lead: Alejandro Abdelnur, Sun Microsystems, Inc.
Alejandro Abdelnur, Sun Microsystems, Inc.Spec Lead: Wesley Budziwojski, Sun Microsystems, Inc.
Description: To enable interoperability between Portlets and Portals, this specification will define a set of APIs for Portal computing addressing the areas of aggregation, personalization, presentation and security.
Spec Lead: Martin Scott Nicklous, IBM
Description: The proposed specification will define a JDBC Optional Package for Java 2 Micro Edition (J2ME), Connected Device Configuration (CDC) Foundation Profile.
Spec Lead: Lance Andersen, Oracle
Description: Specifies a standard API to access content repositories in JavaTM 2 independently of implementation.
Spec Lead: David Nuescheler, Day Software, Inc.
David Nuescheler, Day Software, Inc.Description: This JSR defined JCP version 2.5. Its overriding goal was to ensure that the Process document was in sync with the JSPA 2 created by JSR 99.
Spec Lead: Patrick Curran, Oracle
Description: The purpose of this specification is to define an optional package that provides standard access from J2ME to web services.
Spec Lead: Jean-Yves Bitterlich, Oracle
Description: The Streaming API for XML (StAX) is a Java based API for pull-parsing XML.
Spec Lead: Larry Cable, BEA Systems
Spec Lead: Thorick Chow, BEA Systems
Description: A specification for APIs for monitoring and management of the JavaTM virtual machine.
Spec Lead: Flavio Bergamaschi, IBM
Description: A metadata facility for the JavaTM Programming Language would allow classes, interfaces, fields, and methods to be marked as having particular attributes.
Spec Lead: Alex Buckley, Oracle
Description: Define the major features of the J2SETM "Tiger" release (J2SE 5.0).
Spec Lead: Mark Reinhold, Sun Microsystems, Inc.
Mark Reinhold, Sun Microsystems, Inc.Description: This specification will provide J2ME applications with APIs for security and trust services through the integration of a Security Element.
Spec Lead: Saqib Ahmad, Oracle
Spec Lead: Roman Zelov, Sun Microsystems, Inc.
Description: Defines an optional package that will facilitate the emergence of the market for the development of compelling games on mobile phones. The API shall work with MIDP1.0.
Spec Lead: Thomas Landspurg, In-Fusio SA
Description: An Optional Package that enables developers to write mobile location-based applications for resource-limited devices. The API works on the J2ME CLDC v1.1 and CDC configurations.
Spec Lead: Kimmo Loytana, Nokia Corporation
Kimmo Loytana, Nokia CorporationDescription: SIP API for J2ME defines a multipurpose SIP API for J2ME clients. It enables SIP applications to be executed in memory limited terminals, especially targeting to mobile phones.
Spec Lead: Erkki Rysa, Nokia Corporation
Description: This JSR defines an annotated JavaTM format that that uses JavaTM Language Metadata (JSR 175) to enable easy definition of Java Web Services in a J2EE container.
Spec Lead: Alan Mullendore, Oracle
Description: 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.
Spec Lead: Marquart C Franz, Siemens AG
Description: 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.
Spec Lead: Nataraj Nagaratnam, IBM
Description: This proposed JSR will provide a scalable, small-footprint, interactive 3D API for use on mobile devices.
Spec Lead: Tomi Aarnio, Nokia Corporation
Description: This JSR will provide an overall architectural description as well as an integrated TCK and RI to coordinate selected JCP efforts for the wireless industry.
Spec Lead: Roger Riggs, Oracle
Description: Presence is a generic and protocol-agnostic API for Presence, providing a standard portable and secure interface to control, manage and manipulate Presence information between Presence clients and servers.
Spec Lead: Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory
Description: A protocol-agnostic API for Instant Messaging, this provides a standard portable and secure interface to control, manage and manipulate instant messages between clients through the use of presence servers.
Spec Lead: Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory
Description: To enable interoperability between web servers and access mechanisms, and to facilitate development of device independent web applications, this specification will define a set of APIs for processing CC/PP information.
Spec Lead: Nigel Jacobs, Oracle
Spec Lead: Jerry Raj, Sun Microsystems, Inc.
Description: This JSR will add new large scale funtionality to Java 3D. Possible technologies for inclusion include programmable shading and advanced rendering techniques.
Spec Lead: Kevin Rushforth, Sun Microsystems, Inc.
Description: This defines an optional code package that standardizes application event tracking on a mobile device and the submission of these event records to an event-tracking server via a standard protocol.
Spec Lead: Shai Gotlib, Amdocs Management Ltd.
Shai Gotlib, Amdocs Management Ltd.Description: The API was intended to allow software developers to rapidly develop external Service Provider type applications to interact with the GCCS Service.
Spec Lead: Judith Russell, AePONA
Description: 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).
Spec Lead: Vishal Aggarwal, Hughes Software Systems
Description: 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.
Spec Lead: Adam Bien, Bien, Adam
Description: 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.
Spec Lead: Jorgen Dyst, Appium Technologies AB
Description: This JSR will define a J2ME profile targeting embedded networked devices that wish to support a Java runtime environment, but that do not have graphical display capabilities.
Spec Lead: Thomas Lampart, Cinterion Wireless Modules GmbH
Spec Lead: Jari Lansio, Nokia Corporation
Description: This JSR seeks to define a standard interface by which authentication modules may be integrated with containers and such that these modules may establish the authentication identities used by containers.
Spec Lead: Ron Monzillo, Oracle
Description: The Generic Connection Framework (GCF) Optional Package for J2SE will permit applications that rely on the GCF in J2ME to migrate to J2SE.
Spec Lead: Roger Riggs, Oracle
Description: JSR 198 has the goal of defining a standard IDE API that allows developers to implement IDE plugins once and have them run with any IDE supporting the specification.
Spec Lead: Jose Cronembold, Oracle
Jose Cronembold, OracleDescription: A service provider API that allows a Java program to select and invoke a Java Language Compiler programmatically.
Spec Lead: Jonathan Gibbons, Oracle
Description: 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.
Spec Lead: John Rose, Sun Microsystems, Inc.
Spec Lead: Kumar Srinivasan, Sun Microsystems, Inc.
Description: This JSR proposes four new JavaTM programming language features: enumerations, autoboxing, enhanced for loops and static import.
Spec Lead: Alex Buckley, Oracle
Description: 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.
Spec Lead: Alex Buckley, Oracle
Description: APIs for filesystem access, scalable asynchronous I/O operations, socket-channel binding and configuration, and multicast datagrams.
Spec Lead: Alan Bateman, Oracle
Description: The proposed specification will define a mechanism to support Supplementary Characters as defined in the Unicode 3.1 specification.
Spec Lead: Masayoshi Okutsu, Sun Microsystems, Inc.
Description: This JSR will extend and enhance the "Wireless Messaging API" (JSR-000120)
Spec Lead: Marquart C Franz, Siemens AG
Description: JAXP 1.3 is the next version of JAXP, an implementation independent portable API for processing XML with JavaTM.
Spec Lead: Joe Wang, Sun Microsystems, Inc.
Description: Definition of an annotated Java syntax and APIs for programming business processes in Java.
Spec Lead: Michael Rowley, BEA Systems
Description: This JSR extends J2EETM and J2SETM with business integration SPIs.
Spec Lead: Ron Ten-Hove, Sun Microsystems, Inc.
Spec Lead: Peter Walker, Sun Microsystems, Inc.
Description: The Advanced Graphics and User Interface (AGUI) Optional Package will migrate the core APIs for advanced graphics and user interface facilities from the J2SE platform to the J2ME platform.
Spec Lead: Hakim Mendjeli, Vodafone Group Services Limited
Spec Lead: Roger Riggs, Oracle
Description: 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.
Spec Lead: Thierry Supplisson, Vallent Corporation
Description: Enabling J2METM applications to handle multi-media and web content can give developers and users a seamless and integrated user environment on mobile phones and wireless devices.
Spec Lead: Roger Riggs, Oracle
Description: This specification defines a protocol agnostic messaging API for composing, sending and receiving short messages and multimedia messages. The API shall work on the J2SE and J2EE.
Spec Lead: Hannu Mettala, Nokia Corporation
Description: Effort to define another layer of the J2ME Web Service stack, implementing the 'observable' behavior of a choreographed Web Service on the Device, relative to the message exchange requiring support.
Spec Lead: Ash Parikh, IOPSIS Software Inc.
Description: This JSR is to provide a standard set of APIs for J2ME Devices for representing and manipulating Collaboration Profile and Agreement information described by ebXML CPP/A (Collaboration Protocol Profile/Agreement) documents.
Spec Lead: Ash Parikh, IOPSIS Software Inc.
Description: This JSR will update the JCP Process document to make the process more transparent and efficient.
Spec Lead: Patrick Curran, Oracle
Description: This JSR will update the existing Personal Profile (JSR-62) specification to reflect the J2SETM 1.4 APIs).
Spec Lead: Jon Courtney, Sun Microsystems, Inc.
Jon Courtney, Sun Microsystems, Inc.Spec Lead: Roger Riggs, Oracle
Description: This JSR will update the existing Personal Basis Profile (JSR-129) specification to reflect the J2SETM 1.4 APIs.
Spec Lead: Roger Riggs, Oracle
Description: This JSR defines a revision to the J2ME CDC specification. This JSR provides updates (based on J2SE, v1.4) to the existing core, non-graphical Java APIs for small electronic devices.
Spec Lead: Roger Riggs, Oracle
Description: This JSR defines a revision to the J2ME Foundation Profile. This JSR provides updates (based on J2SE, v1.4) to the existing core, non-graphical Java APIs for small electronic devices.
Spec Lead: Roger Riggs, Oracle
Description: The purpose of Enterprise JavaBeans (EJB) 3.0 is to improve the EJB architecture by reducing its complexity from the developer's point of view.
Spec Lead: Linda DeMichiel, Oracle
Linda DeMichiel, OracleSpec Lead: Michael Keith, Oracle
Description: 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.
Spec Lead: Lance Andersen, Oracle
Description: JAXB 2.0 is the next version of JAXB, The JavaTM Architecture for XML Binding. This JSR proposes additional functionality while retaining ease of development as a key goal.
Spec Lead: Martin Grebac, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Mike Grogan, Sun Microsystems, Inc.
Description: The JAX-WS 2.0 specification is the next generation web services API replacing JAX-RPC 1.0.
Spec Lead: Jitendra Kotamraju, Oracle
Description: 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.
Spec Lead: Maxim Orgiyan, Oracle
Spec Lead: Marc Van Cappellen, DataDirect Technologies
Description: This specification will define an optional package API for rendering scalable 2D vector graphics, including image files in W3C Scalable Vector Graphics (SVG) format.
Spec Lead: Juha Eskelinen, Nokia Corporation
Description: An API and associated metadata format for declaratively binding and accessing data in J2EETM applications.
Spec Lead: John Smiljanic, Oracle
Description: This specification will define a profile that will extend and enhance the "J2METM Information Module Profile" (JSR-195).
Spec Lead: Thomas Lampart, Cinterion Wireless Modules GmbH
Description: Enabling application developers to initiate mobile payment transactions in J2METM applications.
Spec Lead: Jean-Yves Bitterlich, Oracle
Description: Enabling J2METM applications to access native data synchronization implementation
Spec Lead: Jens Paetzold, Oracle
Description: Java bindings to the OpenGL native 3D graphics library.
Spec Lead: Kenneth Russell, Sun Microsystems, Inc.
Description: Create a predictable management environment for mobile devices capable of installing, executing, profiling, updating, and removing JavaTM and associated native components in the J2METM Connected Device Configuration.
Spec Lead: Venkat Amirisetty, Motorola
Spec Lead: Erkki Rysa, Nokia Corporation
Description: This JSR defines an extension of the J2EE platform for the purposes of remotely monitoring and managing the software on mobile devices.
Spec Lead: Jens Paetzold, Oracle
Description: This specification will define an optional package for advanced multimedia functionality which is targeted to run as an supplement in connection with MMAPI (JSR-135) in J2ME/CLDC environment.
Spec Lead: Erkki Rysa, Nokia Corporation
Description: Defines core infrastructure APIs for heterogeneous data access that supports common application design patterns and supports higher-level tools and frameworks.
Spec Lead: Kelvin Goodson, IBM
Spec Lead: Radu Preotiuc-Pietro, Oracle
Description: 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.
Spec Lead: Anthony Lai, Oracle
Spec Lead: Naresh Revanuru, Oracle
Description: A work manager API providing for execution of concurrent work items within managed environments.
Spec Lead: Chris D Johnson, IBM
Spec Lead: Naresh Revanuru, BEA Systems
Description: This JSR defines an API that provides culturally correct data formatting, sorting of text strings and application resource processing for J2ME MIDlets running in MIDP over CLDC.
Spec Lead: Jere Kapyaho, Nokia Corporation
Jere Kapyaho, Nokia CorporationDescription: JavaTM bindings to the OpenGL ES (Embedded Subset) native 3D graphics library.
Spec Lead: Roger Riggs, Oracle
Description: This JSR is a logical extension to address gaps in JSLEE v1.0 specification. The central area of focus is to specify the Resource Adaptor Architecture API and semantics.
Spec Lead: David Ferry, Open Cloud Limited
Description: 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.
Spec Lead: Guillaume Laforge, VMware
Description: The requested specification will define a J2ME profile based on the Connected Limited Device Configuration (CLDC) that is appropriate for use by small-footprint cable television set top boxes.
Spec Lead: Donald Bleyl, Cox Communications, Inc.
Spec Lead: Jens Paetzold, Oracle
Description: The high level objectives are to make JDO easier to use, closely align JDO with J2EE, standardize JDO's database support, and broaden the scope of JDO.
Spec Lead: Craig Russell, Sun Microsystems, Inc.
Description: This JSR is to develop Java EE 5, the next release of the Java Platform, Enterprise Edition, targeted to ship in the second quarter of 2006.
Spec Lead: Bill Shannon, Sun Microsystems, Inc.
Bill Shannon, Sun Microsystems, Inc.Description: This is the next revision of the JavaServerTM Pages specification. The purpose of JSP 2.1 is to improve alignment with JavaServerTM Faces (JSF) and enhance ease of development.
Spec Lead: Kin-man Chung, Oracle
Description: Enabling J2METM applications to access device management implementations
Spec Lead: Jens Paetzold, Oracle
Description: 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.
Spec Lead: Mark F. Hornick, Oracle
Mark F. Hornick, OracleDescription: This JSR creates a mobile service architecture and platform definition for the high volume wireless handsets continuing the work started in JSR-185 and enhancing the definition with new technologies.
Spec Lead: Edin Bektesevic, Vodafone Group Services Limited
Spec Lead: Erkki Rysa, Nokia Corporation
Description: This JSR defines the next generation of the Mobile Service Architecture and platform created in JSR 248.
Spec Lead: Edin Bektesevic, Vodafone Group Services Limited
Spec Lead: Erkki Rysa, Nokia Corporation
Description: This JSR will develop annotations for common semantic concepts in the J2SE and J2EE platforms that apply across a variety of individual technologies.
Spec Lead: Rajiv Mordani, Oracle
Description: Standard for defining and using complex pricing data and business rules, enabling integration, allowing business differentiating extensions. Addresses usage-based business model needs, for communications and entertainment industries and utilities.
Spec Lead: John Wilmes, Ceon Corporation
Description: This JSR is an update to the 1.1 version of the JavaServer Faces specification. Its scope goes beyond a JCP maintenance release, but is short of a new feature release.
Spec Lead: Edward Burns, Oracle
Spec Lead: Roger Kitain, Oracle
Description: This JSR creates a mobile telephony API and platform definition which utilizes common telephony features and is small and simple to suite to high volume devices with limited resources.
Spec Lead: Jean-Yves Bitterlich, Oracle
Spec Lead: Brian Deuser, Motorola
Description: Provide an API that allows network discovery applications to be developed and integrated with other OSS/J enabled applications.
Spec Lead: Andrew Paterson, Nakina Systems
Spec Lead: Sergio Pellizzari, Nakina Systems
Spec Lead: Yves Thibeault, Nakina Systems
Description: 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.
Spec Lead: Eamonn McManus, Oracle
Description: The API provides general Sensor API that extends the usability and choice of sensors for J2ME applications. It defines generic sensor functionality optimized for the resource-constrained devices like mobile devices.
Spec Lead: Pia Niemela, Nokia Corporation
Description: This specification will define J2ME Optional Packages for contactless communication, one package for bi-directional communication and the other for accessing read-only information.
Spec Lead: Jaana Majakangas, Nokia Corporation
Jaana Majakangas, Nokia CorporationDescription: The Mobile User Interface Customization API provides a way to query and modify the user interface customization properties of a mobile device or platform.
Spec Lead: Jere Kapyaho, Nokia Corporation
Jere Kapyaho, Nokia CorporationDescription: The purpose of this JSR is to define an API that enables communication between mobile devices in a peer-to-peer ad-hoc network environment.
Spec Lead: Volker Bauche, Oracle
Description: 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.
Spec Lead: Danny Coward, Oracle
Description: 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.
Spec Lead: Mike Grogan, Sun Microsystems, Inc.
Spec Lead: Arun Gupta, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Eamonn McManus, Oracle
Description: The Fault Management API provides for the monitoring and management of alarms within an information or a telecommunications network.
Spec Lead: Marc Flauw, Hewlett-Packard
Description: This JSR defines an interface to an Order Management component, with specific extensions for activation and work order management use-cases.
Spec Lead: Andreas Ebbert-Karroum, codecentric AG
Description: This specification aims to standardize a basic framework in Java for utilizing the Web services constraints and capabilities.
Spec Lead: Sanjay Patil, SAP AG
Spec Lead: Umit Yalcinalp, SAP AG
Description: The purpose of this JSR is to define an API to access and manage the message boxes of the mobile device and their content.
Spec Lead: Michael Lagally, Oracle
Description: JSPTM Tag Library for accessing Web Services
Spec Lead: Dhiru Pandey, Sun Microsystems, Inc.
Description: APIs for APDU based communication with Smart Cards
Spec Lead: Valerie Peng, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Joe Darcy, Oracle
Description: The Umbrella JSR for the JavaTM SE 6 release.
Spec Lead: Mark Reinhold, Sun Microsystems, Inc.
Mark Reinhold, Sun Microsystems, Inc.Description: This JSR will specify the 3rd generation Mobile Information Device Profile, expanding upon the functionality in all areas as well as improving interoperability across devices.
Spec Lead: Paul Su, Aplix Corporation
Description: This specification will define an optional package in J2ME/MIDP/CLDC environment to provide functionality to handle broadcast content, e.g. to view digital television and to utilize its rich features and services.
Spec Lead: Antti Rantalahti, Nokia Corporation
Antti Rantalahti, Nokia CorporationSpec Lead: Ivan Wong, Motorola
Description: 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.
Spec Lead: Tor Norbye, Oracle
Description: This specification will standardize BeanShell, a Java syntax compatible scripting language for the Java platform.
Spec Lead: Patrick Niemeyer, Niemeyer, Patrick D.
Description: This JSR specifies Java packages for modeling and working with standard measures known as units.
Spec Lead: Jean-Marie Dautelle, Dautelle, Jean-Marie
Spec Lead: Werner Keil, Keil, Werner
Description: Defines a standard mechanism for associating design-time information with JavaServerTM Faces components.
Spec Lead: Jeffrey Stephenson, Oracle
Description: 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.
Spec Lead: Alex Buckley, Oracle
Description: RM API will provide a simple interface for resource reclamation, accounting, and monitoring in a Java ME platform that requires resource management for multiple applications.
Spec Lead: Ho An, Samsung Electronics Corporation
Spec Lead: Hobum (Vincent) Kwon, Samsung Electronics Corporation
Description: A new high-level API for connection services via frameworks supporting identity based services, discovery, and authentication. The API supports Service Oriented Architectures (SOA) and other similar network service application models.
Spec Lead: Pia Niemela, Nokia Corporation
Spec Lead: Jens Paetzold, Oracle
Description: This JSR provides a common general purpose XML API for the next generation of mobile devices.
Spec Lead: Jean-Yves Bitterlich, Oracle
Spec Lead: Pia Niemela, Nokia Corporation
Description: This JSR provides a high-level API to access IP Multimedia Subsystem (IMS) services. This API hides IMS technology details and exposes service-level support to enable easy development of IMS applications.
Spec Lead: Piotr Kessler, Ericsson AB
Spec Lead: Stefan Svenberg, Ericsson AB
Description: Fill some minor gaps in the RTSJ
Spec Lead: Peter Dibble, TimeSys Corporation
Description: As the version 2.0 of the Content Repository for Java Technology API, the aim is to further expand and refine the specification based on feedback from the community.
Spec Lead: David Nuescheler, Day Software, Inc.
David Nuescheler, Day Software, Inc.Description: 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.
Spec Lead: Grzegorz Czajkowski, Google Inc.
Description: The Performance Management API provides for the monitoring and management of the performance of an information or telecommunications network.
Spec Lead: Dave Raymer, Motorola
Description: Version 2.0 of the Portlet Specification plans to align with J2EE 1.4, integrate other new JSRs relevant for the portlet, and align with the WSRP specification V 2.0.
Spec Lead: Martin Scott Nicklous, IBM
Description: This specification will define an optional package for rendering enhanced 2D vector graphics and rich media content based on select features from SVG Mobile 1.2, with primary emphasis on MIDP.
Spec Lead: Juha Eskelinen, Nokia Corporation
Description: This specification will define a mechanism that enables a systems developer to include multiple Configurations and Profiles on a single device, using one set of developed components.
Spec Lead: Andre Kruetzfeldt, Aplix Corporation
Description: This specification is an enhancement to the SIPServlet specification. The central focus of this JSR is to enhance the existing SIPServlet specification with new requirements determined by the industry.
Spec Lead: Yannis Cosmadopoulos, Oracle
Spec Lead: Amitha Pulijala, Oracle
Description: This JSR enables creation of Java ME applications which combine Web UI markup technologies with Java code. The intent is to leverage the W3C Compound Document Format (CDF) specification.
Spec Lead: Jean-Yves Bitterlich, Oracle
Description: Establish a JCP specification for a dynamic component framework supporting existing Java SE environments based on the OSGi dynamic component model specifications.
Spec Lead: Thomas Watson, IBM
Description: Add a new bytecode, invokedynamic, that supports efficient and flexible execution of method invocations in the absence of static type information.
Spec Lead: John Rose, Sun Microsystems, Inc.
Description: This specification defines an optional package that enables the developers to use new enhanced location-based features on the JavaTM ME devices.
Spec Lead: Jaana Majakangas, Nokia Corporation
Jaana Majakangas, Nokia CorporationDescription: Language extensions in support of information hiding and separate compilation.
Spec Lead: Alex Buckley, Oracle
Description: Provide an API that allows two properties of two beans to stay in sync.
Spec Lead: Peter Zhelezniakov, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Alexander Potochkin, Sun Microsystems, Inc.
Description: This new revision of M3G (JSR-184) will expose the latest graphics hardware features on high-end devices, while improving performance and memory usage on the low end.
Spec Lead: Tomi Aarnio, Nokia Corporation
Description: This JSR defines the API set for Telematics Service on mobile devices.
Spec Lead: Dave Kim, SK Telecom Co., Ltd.
Spec Lead: Young Min Park, SK Telecom Co., Ltd.
Description: The purpose of this specification is to unify the JSF managed bean component model with the EJB component model, resulting in a significantly simplified programming model for web-based applications.
Spec Lead: Gavin King, RedHat
Description: This specification will define an optional package for developing JavaTM ME applications which utilize or interoperate with DRM agents that separately exist in devices.
Spec Lead: Jea Un Kim, LG Electronics Inc.
Spec Lead: Dnyanesh R Pathak, LG Electronics Inc.
Description: The Portlet Bridge Specification for JavaServer Faces defines the semantics of a JSR 168/JSR 286 portlet that proxies for JSF artifacts.
Spec Lead: Michael Freedman, Oracle
Description: This specification creates a J2METM capability, based on the Real-Time Specification for Java (JSR-1), containing minimal features necessary for safety critical systems capable of certification, e.g., DO-178B.
Spec Lead: C. Douglass Locke, The Open Group
Description: This JSR will define a meta-data model and API for JavaBeanTM validation based on annotations, with overrides and extended meta-data through the use of XML validation descriptors.
Spec Lead: Emmanuel Bernard, RedHat
Description: This JSR extends the interfaces defined in JSR253 (Mobile Telephony API) to cover additional use cases and features not covered in that JSR.
Spec Lead: Brian Deuser, Motorola
Description: 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.
Spec Lead: William Pugh, Pugh, William
Description: This JSR proposes a variety of changes and adjustments to the JCP.
Spec Lead: Patrick Curran, Oracle
Description: This JSR provides API's for initiating and controlling data sessions in a mobile device and providing applications control over wireless network selection.
Spec Lead: Brian Deuser, Motorola
Description: 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.
Spec Lead: Alex Buckley, Oracle
Spec Lead: Michael Ernst, Ernst, Michael
Description: This Specification is a protocol agnostic API for Media Server Control. It provides a portable interface to create media rich applications with IVR, Conferencing, Speech Recognition, and similar features.
Spec Lead: Marc Brandt, Hewlett-Packard
Spec Lead: Tomas Ericson, Oracle
Description: This JSR will provide a new and improved date and time API for Java.
Spec Lead: Stephen Colebourne, Colebourne, Stephen
Spec Lead: Michael Nascimento Santos, Santos, Michael Nascimento
Description: This JSR will develop an API for providing support for RESTful(Representational State Transfer) Web Services in the Java Platform.
Spec Lead: Marek Potociar, Oracle
Description: 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.
Spec Lead: Ron Ten-Hove, Sun Microsystems, Inc.
Spec Lead: Peter Walker, Sun Microsystems, Inc.
Description: This JSR is to develop Java EE 6, a release of the Java Platform, Enterprise Edition targeted to ship in 2008.
Spec Lead: Roberto Chinnici, Oracle
Spec Lead: Bill Shannon, Sun Microsystems, Inc.
Bill Shannon, Sun Microsystems, Inc.Description: This JSR is an update to the 1.2 version of the JavaServer Faces specification. This is the first major revision of the JavaServer Faces specification since JSR 127.
Spec Lead: Edward Burns, Oracle
Spec Lead: Roger Kitain, Oracle
Description: This JSR will be an update to the existing Servlet 2.5 specification.
Spec Lead: Rajiv Mordani, Oracle
Description: This JSR is to develop Java EE 6, a release of the Java Platform, Enterprise Edition targeted to ship in 2008.
Spec Lead: Roberto Chinnici, Oracle
Spec Lead: Bill Shannon, Oracle
Description: The Java Persistence API is the Java API for the management of persistence and object/relational mapping for Java EE and Java SE environments.
Spec Lead: Linda DeMichiel, Oracle
Linda DeMichiel, OracleDescription: Enterprise JavaBeans is an architecture for the development and deployment of component-based business applications.
Spec Lead: Linda DeMichiel, Oracle
Linda DeMichiel, OracleDescription: 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.
Spec Lead: Jens Jensen, Ericsson AB
Description: This specification will define a high level, lightweight services and management framework API's that will provide JME based devices the ability to manage long running applications and services.
Spec Lead: Roger N. Mahler, AT&T
Description: 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.
Spec Lead: Ronald Toegl, IAIK Graz University of Technology
Description: 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.
Spec Lead: Binod PG, Sun Microsystems, Inc.
Spec Lead: Sivakumar Thyagarajan, Sun Microsystems, Inc.
Description: 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.
Spec Lead: Hiroki Suguri, Suguri, Hiroki
Description: This JSR defines the API set for MIDlet activation functionality on idle screen.
Spec Lead: Dave Kim, SK Telecom Co., Ltd.
Description: This specification will define a high level, IMS Communications Enabler framework API that will provide Java ME based devices effortless access to a set of essential IMS Communication Enablers.
Spec Lead: Martin Gunnang, Ericsson AB
Spec Lead: Niclas Palm, Ericsson AB
Description: A standard Java API designed to support the generation and consumption of post mortem or snapshot Java diagnostic artefacts.
Spec Lead: Steve Poole, IBM
Description: This JSR will enable Java application to interact with dynamic content delivery (DCD) client implementation in user's device.
Spec Lead: Dave Kim, SK Telecom Co., Ltd.
Description: This JSR defines an interface to Change Management Systems handling and approving Requests for Changes.
Spec Lead: Christian Klaus, Ascom Deutschland GmbH
Description: The Portlet 2.0 Bridge defines the semantics for executing JavaServer Faces views within a portlet.
Spec Lead: Michael Freedman, Oracle
Description: We propose to maximize reusability, testability and maintainability of Java code by standardizing an extensible dependency injection API.
Spec Lead: Rod Johnson, VMware
Spec Lead: Bob Lee, Lee, Bob
Description: 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.
Spec Lead: Jacob Feldman, Feldman, Jacob
Description: The Email Client API (EMC) for Java ME enables Java ME applications to access Email services like sending/receiving of Emails and corresponding notifications.
Spec Lead: Gandhi Kishor Addanki, Samsung Electronics Corporation
Spec Lead: Lakshmi Narayana Thummala, Samsung Electronics Corporation
Description: 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.
Spec Lead: David Nuescheler, Adobe Systems Inc.
David Nuescheler, Adobe Systems Inc.Description: 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.
Spec Lead: Joe Darcy, Oracle
Description: Extend the Java language to support compact lambda expressions (closures), as well as related language and library features to enable the Java SE APIs to use lambda expressions effectively.
Spec Lead: Brian Goetz, Oracle
Description: The Umbrella JSR for the seventh edition of the Java SE Platform
Spec Lead: Mark Reinhold, Oracle
Description: The Umbrella JSR for the eighth edition of the Java SE Platform
Spec Lead: Mark Reinhold, Oracle
Description: The Java Persistence API is the Java API for the management of persistence and object/relational mapping in Java EE and Java SE environments.
Spec Lead: Linda DeMichiel, Oracle
Linda DeMichiel, OracleDescription: This JSR will develop the next version of JAX-RS, the API for for RESTful (Representational State Transfer) Web Services in the Java Platform.
Spec Lead: Santiago Pericas-Geertsen, Oracle
Spec Lead: Marek Potociar, Oracle
Description: This JSR is to develop the next version of Java Servlets - Java Servlets 3.1
Spec Lead: Shing Wai Chan, Oracle
Spec Lead: Rajiv Mordani, Oracle
Description: This is an update to Expression Language 2.2, currently part of JSR 245, JavaServer Page (JSP) 2.2.
Spec Lead: Kin-man Chung, Oracle
Description: This JSR will develop Java EE 7, the next version of the Java Platform, Enterprise Edition.
Spec Lead: Linda DeMichiel, Oracle
Linda DeMichiel, OracleSpec Lead: Bill Shannon, Oracle
Description: This is an update to the Java Message Service API, an existing API for accessing enterprise messaging systems from Java programs.
Spec Lead: Nigel Deakin, Oracle
Description: This JSR is an update to the 2.1 version of the JavaServer Faces specification. This is the first major revision of the JavaServer Specification since JSR 314.
Spec Lead: Edward Burns, Oracle
Description: Enterprise JavaBeans is an architecture for the development and deployment of component-based business applications.
Spec Lead: Marina Vatkina, Oracle
Description: Updates and clarifications to CDI 1.0 along much requested features.
Spec Lead: Pete Muir, RedHat
Description: This JSR proposes an API for interacting with in-memory and disk-based distributed data grids.
Spec Lead: Manik Surtani, RedHat
Description: This JSR proposes a variety of changes and adjustments to the Java Community Process.
Spec Lead: Patrick Curran, Oracle
Description: 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.
Spec Lead: Emmanuel Bernard, RedHat
Description: 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.
Spec Lead: Mitch Upton, Oracle
Description: This JSR will develop the Identity API for the Java Platform.
Spec Lead: Ron Monzillo, Oracle
Description: This JSR specifies a programming model for batch applications and a runtime for scheduling and executing jobs.
Spec Lead: Chris Vignola, IBM
Description: 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.
Spec Lead: Jitendra Kotamraju, Oracle
Description: Provides an API for representing, transporting, and performing comprehensive calculations with Money and Currency.
Spec Lead: Victor Grazi, Credit Suisse
Description: Since Java is One Platform this JSR will merge the two Executive Committees into one, and will reduce the total number of EC members.
Spec Lead: Patrick Curran, Oracle
Description: The Java API for WebSocket JSR will define a standard API for creating WebSocket applications.
Spec Lead: Danny Coward, Oracle
Description: 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.
Spec Lead: Alex Buckley, Oracle
Description: Maintenance revision for the JavaTM Servlet API Specification, version 2.2.
Spec Lead: Danny Coward, Oracle
Description: Maintenance revision for the JavaTM Servlet API Specification, version 2.2.
Spec Lead: Danny Coward, Oracle
Description: Maintenance revision 1.2 for the JavaMailTM API.
Spec Lead: Bill Shannon, Oracle
Description: Maintenance revision for the Enterprise JavaBeansTM Specification, version 1.1.
Spec Lead: Linda DeMichiel, Oracle
Linda DeMichiel, OracleDescription: The Errata Sheet for 2000.04.28.
Spec Lead: Eduardo Pelegri-Llopart, Sun Microsystems, Inc.
Description: Revisions to the JTA specification.
Spec Lead: Paul Parkinson, Oracle
Description: Minor changes to the RTP section.
Spec Lead: Marc Owerfeldt, Sun Microsystems, Inc.
Description: The Maintenance Review of the JSPA revisions.
Spec Lead: Jonathan Nimer, Sun Microsystems, Inc.
Description: Errata Sheet of JDBC 2.1 for Maintenance review.
Spec Lead: Lance Andersen, Oracle
Description: This details the specification differences between Ladybird and Kestrel.
Spec Lead: Alan Sommerer, Sun Microsystems, Inc.
Description: Version 1.3 of the Java 3D API.
Spec Lead: Kevin Rushforth, Sun Microsystems, Inc.
Description: This is the Maintenance Revision of the JCP 2.0 EC Voting rules.
Spec Lead: Patrick Curran, Oracle
Description: JavaTM Message Service API Errata.
Spec Lead: Nigel Deakin, Oracle
Description: Details of specification changes made in version 1.4 ("Merlin") of the JavaTM 2 Platform, Standard Edition.
Spec Lead: Alan Sommerer, Sun Microsystems, Inc.
Description: Details of specification changes made in version 1.4 ("Merlin") of the JavaTM 2 Platform, Standard Edition.
Spec Lead: Alan Sommerer, Sun Microsystems, Inc.
Description: Details of specification changes made in version 1.4 ("Merlin") of the JavaTM 2 Platform, Standard Edition.
Submitter: Alan Sommerer, Sun Microsystems, Inc.
Description: Define the major features of the J2SETM 1.4 release.
Spec Lead: Alan Sommerer, Sun Microsystems, Inc.
Description: A description of the new APIs that are being introduced in JavaMail.
Spec Lead: Bill Shannon, Sun Microsystems, Inc.
Bill Shannon, Sun Microsystems, Inc.Description: Maintenance Review of the JMF specification, version 2.1.1.
Spec Lead: Babu Srinivasan, Sun Microsystems, Inc.
Description: This is a Maintenance Revision of the Implementing Enterprise Web Services 1.1 Specification.
Spec Lead: Dhiru Pandey, Sun Microsystems, Inc.
Description: Maintenance version of the Java Communication API specification,version 2.0.3
Spec Lead: Vincent Zhang, Sun Microsystems, Inc.
Description: Descriptions of specification changes being made in version 1.4.2 ("Mantis") of the JavaTM 2 Platform, Standard Edition (J2SETM).
Spec Lead: Danny Coward, Oracle
Description: Maintenance review of changes to the JavaTM Virtual Machine Specification, Second Edition for J2SE 1.5
Spec Lead: Alex Buckley, Oracle
Description: JavaBeans Activation Framework 1.1 proposes a few minor changes to the JAF APIs to address the most commonly requested enhancements.
Spec Lead: Bill Shannon, Sun Microsystems, Inc.
Bill Shannon, Sun Microsystems, Inc.Description: Maintenance of the Java 3D specification.
Spec Lead: Kevin Rushforth, Sun Microsystems, Inc.
Description: The maintenance of the Java TV specification.
Spec Lead: Michael Lagally, Oracle
Spec Lead: Jens Paetzold, Oracle
You are viewing a mobilized version of this site...
View original page here
