JavaData & JavaLatest JSRs Released by the JCP

Latest JSRs Released by the JCP content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More.

Here are the latest Java Specification Requests available for final release by the Java Community Process:

JSR 147, Workspace Versioning and Configuration Management

Target Java platform: J2EE/J2SE

Description: Workspace Versioning and Configuration Management provides client support for creating and manipulating sets of version-controlled files and web resources.

For more information go to

JSR 248, Mobile Service Architecture

Target Java platform: Mobile Handsets.

Description: 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.

For more information go to

JSR 270, Java SE 6 Release Contents

Target Java platform: This specification will define the next release of the J2SE platform.

Description: This is the Umbrella JSR for the Java(TM) SE 6 release. The specification will define the feature set for the next major release of the Java 2 Standard Edition platform, code named “Mustang”, which is targeted to ship in 2006. Mustang is one of a ongoing series of J2SE feature releases. The goal is to ship feature releases on a regular 18-24 month cycle, with each release including a combination of quality improvements and new features.

This JSR will not itself define any new features or enhancements; it will, rather, enumerate features and enhancements defined in other JSRs or through the JCP maintenance process. It is expected that most of the effort in the Mustang release will be toward product quality (bug fixing) and stability, with relatively less work going into new APIs and other kinds of features.

For more information go to

JSR 269, Pluggable Annotation Processing API

Target Java platform: J2SE

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. In order to support annotation processing at build-time, this JSR will define APIs to allow annotation processors to be created using a standard pluggable API. This will simplify the task of creating annotation processors and will also allow automation of the discovery of appropriate annotation processors for a given source file.

For more information go to

JSR 268, Java Smart Card I/O API

Target Java platform: J2SE 5.0 and later.

Description: APIs for APDU based communication with Smart Cards. This JSR will define a Java API for APDU based communication. The API will be designed to be compact but sufficiently complete to satisfy the majority of applications. We envision an API roughly equivalent in features to the resource manager in the PC/SC Workgroup specifications.

For more information go to

JSR 202, Java Class File Specification Update

Target Java platform: J2SE

Description: This JSR will make incremental updates to the Java(TM) class file format. This will principally consist of increasing certain class file size limits and adding support for split verification. This JSR will revise the Java(TM) Virtual Machine Specification by making some incremental updates to the Java class file specification. This work is targeted at the J2SE 1.5 “Tiger” release.

For more information go to

JSR 221, JDBC API 4.0 Specification

Target Java platform: This specification is intended to become part of the Java SE 6 (“Mustang”).

Description: The stated goal of this specification is to provide an improved developer experience while working with relational SQL data stores from the Java platform. To meet this requirement, our primary attention will be given to determining key issues that developers encounter while using the JDBC API and addressing the issues by making adequate provision in the areas detailed below:

  • Management of JDBC Technology Enabled Drivers
  • Connection Management
  • Persistence and Update mechanisms
  • Close Association with JDBC RowSet implementations
  • Maintain focus on SQL control
  • Ensure JDBC backward compatibility

For more information go to

Get the Free Newsletter!

Subscribe to Developer Insider for top news, trends & analysis

Latest Posts

Related Stories