 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 270: JavaTM SE 6 Release Contents
JCP version in use: 2.9 Java Specification Participation Agreement version in use: 2.0 Description: The Umbrella JSR for the JavaTM SE 6 release. Team
The following updates have been made to the original proposal:
2014.09.22: Maintenance Leads: Iris Clark, Mark Reinhold E-Mail Address:
iris.clark Telephone Number: +1 408 276 3909, +1 408 276 7256 Fax Number: - 2010.02.15:The Maintenance Lead of this JSR changed from Sun Microsystems to Oracle America, Inc. Maintenance Lead: Mark Reinhold E-Mail Address:
mark.reinhold Telephone Number: +1 408 276 7256 Fax Number: - 2006.12.11:This JSR was completed under JCP 2.6. 2006.10.24: 2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.The Java Platform, Standard Edition ("Java SE") is the core Java platform for desktop and server environments. The Java SE specification defines a wide range of general purpose APIs and also includes the Java Language Specification and the Java Virtual Machine Specification. In addition to being used standalone on servers, Java SE is also used as the base for Java Platform, Enterprise Edition ("Java EE"). Within the device and embedded space, Java SE technologies (including APIs, language features, and JVM features) are often reused within Java Platform, Micro Edition ("Java ME") JSRs.The following is an overview of Sun's planned license terms and conditions for Java SE 6.0, for use in general purpose desktop and server environments: 1. Binaries for the Java SE 6 Java Runtime Environment (JRE) will be made available under a Sun Microsystems Inc. Binary Code License, for Windows, Linux, and Solaris, at zero cost. 2. Binaries for the Java SE 6 Java Developer Kit (JDK) will be made available under Sun Microsystems Inc. Binary Code License, for Windows, Linux, and Solaris, at zero cost. 3. Java SE 6 Reference Implementation (RI) and Technology Compatibility Kit (TCK) sources will be made available to Sun's existing TLDA licensees for such technology according to their TLDA terms. 4. The RI sources will be available under the Java Research License to encourage academic experimentation and research, at zero cost. 5. The RI sources will be made available under a version of the Java Distribution License, at zero cost. 6. Licensing of the RI is not required for licensing of the TCK. 7. Nothing in the licensing terms will prevent open source projects from creating and distributing their own compatible open source implementations of Java SE 6, using standard open source licenses. (Yes, you can create your own open source implementation of Java SE 6 if you really want to. But we're also doing everything we can to make it easy for you to use the original RI sources! See http://jdk6.dev.java.net.) 8. Earlier releases of Java SE have designated certain source files as being "Shared Source". "Shared Source" is a concept that is used to foster compatibility by requiring that all implementors use unmodified copies of particular source files. Java SE 6 will not contain any "Shared Source" source files. This means that independent implementations of the Java SE 6 specification will not be required to include any source code from Sun. 9. The Java SE 6 TCK will be licensed to commercial entities at $100K per year. This includes trademark and branding rights and a minimal level of TCK support. More extensive TCK support offerings are also available. 10. The Java SE 6 TCK will be offered for license at no charge, with trademark and branding rights, but without support, to qualified not-for-profit entities (including not-for-profit academic institutions) and qualified individuals engaged in efforts to create compatible implementations of the Java SE 6 Specification. 11. Java SE 6 includes JSR 199 "Java Compiler API" and JSR 269 "Pluggable Annotation Processing API". The RIs for the Java Compiler API and the Pluggable Annotation Processing API are included in the RI for Java SE 6, and the TCKs for Java Compiler API and Pluggable Annotation Processing API are included in the TCK for Java SE 6. However, as described in the final approval ballot materials for JSRs 169 and 199, the TCKs for JSRs 169 and 199 will additionally be released stand-alone. 12. Java SE 6 includes JSR 223 "Scripting for the Java Platform". The RI for Scripting for the Java Platform is included in the RI for Java SE 6, and the TCKs for the Scripting for the Java Platform is included in the TCK for Java SE 6. However, as described in the final approval ballot materials for JSR 223, the RI and TCK for JSR 223 will additionally be released standalone. 2006.09.12: The title and summary were updated from the following: JavaTM SE 6 ("Mustang") Release Contents The Umbrella JSR for the JavaTM SE 6 ("Mustang") release.
2.13 Please describe the anticipated schedule for the development of this specification.Early Draft - Winter 2005 2006.02.14: 2.13 Please describe the anticipated schedule for the development of this specification.Early Draft - Winter 2005
Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification Submitting Member: Sun Microsystems, Inc Name of Contact Person: Mark Reinhold E-Mail Address: mr Telephone Number: +1 408 276 7256 Fax Number: +1 408 276 7700 Specification Lead: Mark Reinhold E-Mail Address: mr Telephone Number: +1 408 276 7256 Fax Number: +1 408 276 7700 Initial Expert Group Membership: Google Supporting this JSR: N/A Section 2: Request
2.1 Please describe the proposed Specification:The proposed 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. The JSR expert group will define a specification consisting of a target feature set for Mustang. This target set will be further refined during the early-draft and public review periods and will become the target feature set for the release. The goal is for the Mustang release to include the full target set, but depending upon design and implementation schedules some items may be deferred to a later release if they are unable to make the Mustang schedule. The final specification will reflect the actual content of the Mustang release. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)This specification will define the next release of the J2SE platform. 2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.Representatives from the J2ME and J2EE communities have already been involved in the preliminary planning activities for this release. We look forward to their continued involvement as the work progresses. 2.4 Should this JSR be voted on by both Executive Committees?No 2.5 What need of the Java community will be addressed by the proposed specification?The major themes of the Mustang release are expected to be:
* Diagnosability, Monitoring, and Management * Ease of Development * Enterprise Desktop * XML & Web Services * Transparency Most of these are continuations of successful themes from the J2SE 5.0 ("Tiger") release. The last theme, Transparency, is new and reflects Sun's ongoing effort to evolve the J2SE platform in a more open and transparent manner. 2.6 Why isn't this need met by existing specifications?N/A 2.7 Please give a short description of the underlying technology or technologies:N/A 2.8 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)N/A 2.9 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?No 2.10 Are there any security issues that cannot be addressed by the current security model?None are known at this time. 2.11 Are there any internationalization or localization issues?None are known at this time. 2.12 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?This JSR represents a major revision of the J2SE platform specification. 2.13 Please describe the anticipated schedule for the development of this specification.Early Draft - April 2005 2.14 Please describe the anticipated working model for the Expert Group working on developing this specification.The Expert Group will communicate primarily via e-mail. 2.15 It is important to the success of the community and each JSR that the work of the Expert Group be handled in a manner which provides the community and the public with insight into the work the Expert Group is doing, and the decisions that the Expert Group has made. The Executive Committees would like to ensure Spec Leads understand the value of this transparency and ask that each JSR have an operating plan in place for how their JSR will address the involvement of the community and the public. Please provide your plan here, and refer to the Spec Lead Guide for a more detailed description and a set of example questions you may wish to answer in your plan.Our goal will be to update the publicly-viewable draft of the specification within two weeks of any significant change, together with an explanation of the change. This will start at the beginning of the Early Draft Review period and go right up to the Final Release. Notifications of such changes will be sent to the members' observer alias as a courtesy.
We additionally plan to create a project on java.net in order to publish a FAQ and to host ongoing public discussions. 2.16 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.The RI will be the Java 2, Standard Edition Development Kit (JDK), version 6.0. The TCK will be the Java Compatibility Kit (JCK), version 6. 2.17 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).N/A 2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.The Java 2 Platform, Standard Edition ("J2SE") is the core Java platform for desktop and server environments. The J2SE specification defines a wide range of general purpose APIs and also includes the Java Language Specification and the Java Virtual Machine Specification. In addition to being used standalone on servers, J2SE is also used as the base for Java 2 Platform, Enterprise Edition ("J2EE"). Within the device and embedded space, J2SE technologies (including APIs, language features, and JVM features) are often reused within Java 2 Platform, Micro Edition ("J2ME") JSRs. The following is an overview of Sun's planned license terms and conditions for J2SE 6.0, for use in general purpose desktop and server environments:
2. Binaries for the J2SE 6.0 Java Developer Kit (JDK) will be made available under Sun Microsystems Inc. Binary Code License, for Windows, Linux, and Solaris, at zero cost. 3. J2SE 6.0 Reference Implementation (RI) and Technology Compatibility Kit (TCK) sources will be made available to Sun's existing TLDA licensees for such technology according to their TLDA terms. 4. The RI sources will be available under the Java Research License to encourage academic experimentation and research, at zero cost. 5. The RI sources will be made available under a version of the Java Distribution License, at zero cost. 6. Licensing of the RI is not required for licensing of the TCK. 7. Nothing in the licensing terms will prevent open source projects from creating and distributing their own compatible open source implementations of J2SE 6.0, using standard open source licenses. (Yes, you can create your own open source implementation of J2SE 6.0 if you really want to. But we're also doing everything we can to make it easy for you to use the original RI sources! See http://j2se.dev.java.net.) 8. Earlier releases of J2SE have designated certain source files as being "Shared Source". "Shared Source" is a concept that is used to foster compatibility by requiring that all implementors use unmodified copies of particular source files. J2SE 6.0 will not contain any "Shared Source" source files. This means that independent implementations of the J2SE 6.0 specification will not be required to include any source code from Sun. 9. The J2SE 6.0 TCK will be licensed to commercial entities at $100K per year. This includes trademark and branding rights and a minimal level of TCK support. More extensive TCK support offerings are also available. 10. The J2SE 6.0 TCK will be offered for license at no charge, with trademark and branding rights, but without support, to qualified not-for-profit entities (including not-for-profit academic institutions) and qualified individuals engaged in efforts to create compatible implementations of the J2SE 6.0 Specification. 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.The following JSRs are being considered for inclusion as components of the Mustang Umbrella JSR:
JSR 105: XML Digital Signature The final Mustang specification might not include all of these JSRs, and it might include some JSRs not listed here. 3.2 Explanation of how these items might be used as a starting point for the work.(see above) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
