Printed: Apr 24, 2014
From: http://www.jcp.org/en/jsr/detail?id=176

Standard Format


Community
Expert Group

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 176: J2SETM 5.0 (Tiger) Release Contents

Stage Access Start Finish
Maintenance Draft Review 2 Download page 11 Oct, 2006 13 Nov, 2006
Maintenance Draft Review Download page 21 Mar, 2006 24 Apr, 2006
Final Release Download page 30 Sep, 2004  
Final Approval Ballot View results 31 Aug, 2004 13 Sep, 2004
Proposed Final Draft Download page 24 Jun, 2004  
Public Review 2 Download page 11 May, 2004 10 Jun, 2004
Public Review Download page 04 Feb, 2004 05 Mar, 2004
Community Draft Ballot View results 20 Jan, 2004 26 Jan, 2004
Community Review Login page 19 Dec, 2003 26 Jan, 2004
Expert Group Formation   02 Apr, 2002 18 Jul, 2002
JSR Review Ballot View results 19 Mar, 2002 01 Apr, 2002
Status: Maintenance
JCP version in use: 2.6
Java Specification Participation Agreement version in use: 2.0


Description:
Define the major features of the J2SETM "Tiger" release (J2SE 5.0).

Please direct comments on this JSR to the Spec Lead(s)
Team

Specification Leads
Star Spec Lead Mark Reinhold Sun Microsystems, Inc.
Expert Group
  Apache Software Foundation Apple Computer, Inc. BEA Systems
  Borland Software Corporation Cisco Systems Doederlein, Osvaldo Pinali
  Fujitsu Limited Hewlett-Packard IBM
  Kreileder, Juergen Macromedia, Inc. Nokia Corporation
  Oracle SAP AG SAS Institute Inc.
  SavaJe Technologies Sun Microsystems, Inc. Zukowski, John A.

Updates to the Original Java Specification Request (JSR)

This JSR was completed under JCP 2.1 and moved to JCP 2.6 in Maintenance.

The following information has been updated from the original request.

2.1 Please describe the proposed Specification:

This JSR is to develop a specification for the feature and API set for the next feature release of Java 2 Standard Edition, code named "Tiger", targeted to ship Q3 CY 2004. Tiger is one of a series of feature releases to J2SE. The intention is to ship feature releases on a regular 18 month cycle, with each release including a combination of quality improvements and a small amount of new features.

2.11 Please describe the anticipated schedule for the development of this specification.

Final RI and TCK are proposed for Q3 CY 2004.

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

Various existing JSR API initiatives will be evaluated as potential candidates for Tiger. Amongst the possible candidates for evaluation are:

JSR-003 JavaTM Management Extensions (JMXTM) Specification
JSR-013 Decimal Arithmetic Enhancement
JSR-014 Add Generic Types to the JavaTM Programming Language
JSR-028 JavaTM SASL Specfication
JSR-114 JDBC Rowset Implementations
JSR-133 JavaTM Memory Model and Thread Specification Revision
JSR-163 JavaTM Platform Profiling Architecture
JSR-166 Concurrency Utilities
JSR-174 Monitoring and Management Specification for the JavaTM Virtual Machine
JSR-175 A Metadata Facility for the JavaTM Programming Language
JSR-199 JavaTM Compiler API
JSR-200 Network Transfer Format for JavaTM Archives
JSR-201 Extending the JavaTM Programming Language with Enumerations, Autoboxing, Enhanced for loops and Static Import
JSR-204 Unicode Supplementary Character Support
JSR-206 JavaTM API for XML Processing (JAXP) 1.3

The final specification for Tiger may not include all of these JSRs, and may include some JSRs not present on this list.

Note that this information has been updated from the original request.
Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Section 1. Identification

Submitting Member: Sun Microsystems, Inc./P>

Name of Contact Person: Calvin Austin

E-Mail Address: tiger-jsr@sun.com

Telephone Number: +1 408 276 7010

Fax Number:


Specification Lead: Calvin Austin

E-Mail Address: tiger-jsr@sun.com

Telephone Number: +1 408 276 7010

Fax Number:


Initial Expert Group Membership:

Apple
Compaq
Hewlett-Packard
IBM
Oracle
SAP

Supporting this JSR:

Apache Software Foundation
Apple
BEA Systems
Borland
Caldera Systems
Compaq
Fujitsu
Hewlett-Packard
IBM
IONA Technologies
Doug Lea
Macromedia
Nokia
Oracle
SAP



Section 2: Request

2.1 Please describe the proposed Specification:

NOTE that this information has been updated since the original request.

This JSR is to develop a specification for the feature and API set for the next feature release of Java 2 Standard Edition, code named "Tiger", targeted to ship in 2003. Tiger is one of a series of feature releases to J2SE. The intention is to ship feature releases on a regular 18 month cycle, with each release including a combination of quality improvements and a small amount of new features.

This JSR will not itself define any new APIs, rather it will enumerate APIs defined in other JSRs or through the JCP maintenance process.

It is expected that most of the effort in the Tiger release will be around product quality (bug fixing) and reliability, availability and serviceability with only a relatively small amount of new features and new APIs.

The JSR expert group will define a specification consisting of a target feature and API set for Tiger. This target list will be further refined during community review and public review and will become the target feature set for the Tiger release. The goal is that the Tiger release will include this full target set, but depending on implementation and API design schedules some items may be deferred to a later release if they are unable to make the release schedule for Tiger. The final specification will reflect the final Tiger deliverables.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

This specification defines the next release of the J2SE Platform.

2.3 What need of the Java community will be addressed by the proposed specification?

It is anticipated that the Tiger release will be mainly targeted at the following major themes:

Reliability, Availability, Serviceability
Monitoring and Manageability
Scalability and Performance
XML and Client Web Services
Ease of Development

The reliability, availability and serviceability theme and monitoring and manageability theme is in response to the needs of the growing installed base of mission critical applications using the Java platform.

The scalability and performance theme is focused on improving the server side and client side Java applications runtime

The focus on XML and web services clienst is to ensure that client application written in the Java language can take full advantage of these technologies.

Finally, the Java language and platform have been designed with ease of development in mind, this role of this theme is to drive further enhancements in this area for individual developers and developers of tools.

The Tiger release will be fully compatible with earlier J2SE releases.

2.4 Why isn't this need met by existing specifications?

This is an umbrella JSR for a feature release as described above.

2.5 Please give a short description of the underlying technology or technologies:

The umbrella JSR is aimed at meeting the themes of the release.

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

N/A

2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

N/A

2.8 Are there any security issues that cannot be addressed by the current security model?

N/A

2.9 Are there any internationalization or localization issues?

Updates to existing I18n support

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

The J2SE specification.

2.11 Please describe the anticipated schedule for the development of this specification.

Final RI and TCK are proposed for end 2003

2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.

E-mail, teleconferences, and infrequent meetings.





Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

Note that this information has been updated from this original request on 8 July 2003.

Various existing JSR API initiatives will be evaluated as potential candidates for Tiger. Amongst the possible candidates for evaluation are:

JSR-003 JavaTM Management Extensions (JMXTM) Specification
JSR-013 Decimal Arithmetic Enhancement
JSR-014 Add Generic Types to the JavaTM Programming Language
JSR-101 JavaTM APIs for XML RPC
JSR-105 XML Digital Signature APIs
JSR-106 XML Digital Encryption APIs
JSR-114 JDBC Rowset Implementations
JSR-121 Application Isolation API Specification
JSR-163 JavaTM Platform Profiling Architecture

The final specification for Tiger may not include all of these JSRs, and may include some JSRs not present on this list.

3.2 Explanation of how these items might be used as a starting point for the work.



Section 4: Additional Information (Optional)

4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.

Sun plans to adhere to the proposed new JSPA licensing model for this JSR, including allowing independent implementations, licensing the TCK separately from the RI, minimizing shared code, and licensing any remaining shared code (such as the verifier) on simple non-restrictive licensing terms. In addition Sun plans to make it easier for academic and non-profit groups to obtain access to the RI and TCKs.