The Real-Time Specification for Java extends the JavaTM platform to support both current practice and advanced real-time systems application programming.
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.
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.
The Industrial Automation specification will result in an industry standard for industrial automation that is based on the JavaTM and JiniTM technologies.
Withdrawn with the consent of the Spec Lead. Difficulties in forming an expert group and reaching consensus toward a draft spec hampered the JSR's abilities in successfully navigating the community process.
The Federated Management Architecture (FMA) specifies a storage management platform that will allow vendors to construct storage management applications from standard and custom components.
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.
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.
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.
The J2EETM Connector architecture defines a standard architecture for integrating JavaTM applications with existing back-end Enterprise Information systems.
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.
JAINTM Operations, Administration, and Maintenance (OAM) defines a standard API for provisioning and managing protocol interfaces in the Telecommunications and Internet Industry.
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.
Orthogonal persistence for the JavaTM platform (OPJ) would have provided persistence for the full computational model specified by the JavaTM Language Specification (JLS).
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.
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.
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.
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.
Withdrawn due to lack of interest after the original Spec Lead company was acquired. New Spec Lead company has failed to find a Spec Lead who wants to drive JSR-26 to completion. Expert Group was informed of intent to withdraw JSR-26 and it supported that action.
Withdrawn before work began because the proposal describes a cryptographic system and/or a cryptographic framework whose implementation would be subject to U.S. Export Licensing requirements.
The JAINTM MAP API Specification includes functionality for messaging and location service. The API may be implemented on different protocols, e.g. ETSI MAP and ANSI 41.
Withdrawn 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.
This specification will define a standard platform configuration of the JavaTM 2 platform, Micro Edition (J2METM) for small, resource-limited, connected devices.
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.
The InfoBus 2.0 Specification and release would have added features to the existing InfoBus 1.2 Specification that capitalize on new features found in the J2SETM Platform.
Withdrawn 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.
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.
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.
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.
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.
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.
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.
A new keyword allowing programmers to include assertions describing intended program behavior, which can be checked as programs execute to detect bugs.
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).
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.
This specification establishes standardized tools for correlating JavaTM virtual machine byte code to source code of languages other than the JavaTM programming language.
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.
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.
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.
The Certification Path API provides a set of provider-based APIs for creating, building, and verifying certification paths (also known as "certificate chains").
This JSR was originally proposed a long time ago, but failed to attract a critical mass for an expert group. After a few conference calls, the effort was abandoned.
Phonelets provide developers with a simple API to package, deploy and run Computer Telephony Integration (CTI) applications in a resource and security controlled environment.
This JSR is a proposal to define an Enterprise Java BeanTM (EJBTM) component interface for party information as required by the financial services domain.
Withdrawn 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.
The J2METM RMI Optional Package (RMI OP) provides JavaTM platform to Java platform remote method invocation for Java devices and interoperates with J2SETM RMI.
Its original purpose to define the architecture for Java ME and additional processes for building blocks are not necessary. The Community Review draft contains useful working definitions of Configurations and Profiles and useful rules for subsetting and merging APIs.
JOLAP is a pure Java API for the J2EETM environment that supports the creation and maintenance of OLAP data and metadata, in a vendor-independent manner.
Withdrawn 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.
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.
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.
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.
Define a high-level API for network security in JavaTM 2 Standard Edition RMI, covering basic security mechanisms: authentication (including delegation), confidentiality, and integrity.
The JavaTM 2 Platform, Enterprise Edition Management Specification will provide server vendors and tool vendors with a standard model for managing the J2EE Platform.
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.
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.
本文提供JSR（Java Specification Requests）规范的详细列表下载链接，帮助读者深入理解Java开发中的各项规范，包括JSR的原始内容。
最低0.47元/天 解锁文章
扫一扫
2740
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
