 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 340: Java Servlet 3.1 Specification
JCP version in use: 2.8 Java Specification Participation Agreement version in use: 2.0 Description: This JSR is to develop the next version of Java Servlets - Java Servlets 3.1 Expert Group Transparency: Public Communications Issue Tracking Team
The following information has been updated from the original JSR proposal.
2013.03.05: 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 Specification Lead and Expert Group have moved JSR 340 to JCP 2.8.
2012.04.06: 2.13 Please describe the anticipated schedule for the development of this specification.
Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification Submitting Member: Oracle Name of Contact Person: Rajiv Mordani E-Mail Address: rajiv.mordani Telephone Number: +1 408 276 7204 Fax Number: +1 408 276 4185 Specification Lead: Shing Wai Chan, Rajiv Mordani E-Mail Address: shing.wai.chan Telephone Number: +1 408 276 5598, +1 408 276 7204 Fax Number: -, +1 408 276 4185 Initial Expert Group Membership:
Supporting this JSR: Google Section 2: Request
2.1 Please describe the proposed Specification:This JSR is to develop the next version of Java Servlets - Java Servlets 3.1 Specification. In Servlet 3.0 we made a lot of progress in our goal towards Ease-of-Development, pluggability and security enhancements in the web tier. As a follow up to the release, in this release we plan to address the following areas of the Java Web container:
2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)This specification is targeted for Java EE 7 or higher platforms. 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.This specification targets the Java EE 7 Platform. It will be based on the corresponding release of the Java SE platform. 2.4 Should this JSR be voted on by both Executive Committees?No. Just the SE/EE Executive Committee. 2.5 What need of the Java community will be addressed by the proposed specification?See 2.1 2.6 Why isn't this need met by existing specifications?This specification is an update to the existing Servlet specification. 2.7 Please give a short description of the underlying technology or technologies:The specification would depend on JSR 236 - Concurrency Utilities for Java EE and other features from the Java Platform like NIO2. 2.8 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)javax.servlet.* 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?No. 2.11 Are there any internationalization or localization issues?This JSR will use the I18N support in Java SE. 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 is an update to Servlets 3.0 (JSR 315). 2.13 Please describe the anticipated schedule for the development of this specification.
Note that this section of the JSR has been updated from this original proposal. 2.14 Please describe the anticipated working model for the Expert Group working on developing this specification.The primary means of communication will be email, with conference calls and face-to-face meetings scheduled as needed. We will solicit feedback from the community and leverage the open source development model. 2.15 Provide detailed answers to the transparency checklist, making sure to include URLs as appropriate:We will leverage the collaborative tools provided by the java.net infrastructure. Therein, we will have a public issue tracker for tracking most issues. We will have an EG-private mailing list. The reference implementation will be developed entirely in the public GlassFish project on java.net. The TCK will be developed privately by Oracle. We will leverage the Early Draft feature of JCP 2.6 to allow the public to see the spec in progress. - The public can read the names of the people on the Expert Group. This information will be on on the project page for the JSR. It will also be part of every specification draft. - The Expert Group business is regularly reported on a publicly readable alias. The Expert Group will conduct business on a publicly readable alias. A private alias will be used only for EG-confidential information, as needed. - The schedule for the JSR is publicly available, it's current, and I update it regularly. The schedule will be available on the project page for the JSR. - The public can read/write to a wiki for my JSR. We'll use a public mailing list for comments. - I read and respond to posts on the discussion board for my JSR on jcp.org. We'll track such discussions and respond to them or redirect users to the public comment mailing list. - There is an issue-tracker for my JSR that the public can read. Yes, it will be accessible from the JSR project page. - I have spoken at conferences and events about my JSR recently. No - I am using open-source processes for the development of the RI and/or TCK. Yes, the Reference Implementation will be developed as part of Project GlassFish. The final RI will be available from the download page. - The Update tab for my JSR has links to and information about all public communication mechanisms and sites for the development of my JSR. It will point to the project page for the JSR. 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 delivered as part of the Java EE 7 RI. The TCK will be delivered both standalone and as part of the Java EE 7 TCK. See the business terms for details. 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.Note that this information has been updated from this original proposal. Specification license 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.JSR 315 3.2 Explanation of how these items might be used as a starting point for the work.This is an update to Servlets 3.0 (JSR 315). |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
