 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 176: J2SETM 5.0 (Tiger) Release Contents
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 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 Supporting this JSR: Apache Software Foundation 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 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 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. |
