About JCP
Get Involved
Community Resources
Community News
FAQ
Contact Us
|
|
|
|
| Stage |
Access |
Start |
Finish |
| Final Release |
Download page |
17 Apr, 2017 |
|
| Final Approval Ballot |
View results |
14 Mar, 2017 |
27 Mar, 2017 |
| Proposed Final Draft |
Download page |
09 Mar, 2017 |
|
| Public Review Ballot |
View results |
21 Feb, 2017 |
06 Mar, 2017 |
| Public Review |
Download page |
23 Jan, 2017 |
21 Feb, 2017 |
| Early Draft Review |
Download page |
21 Oct, 2015 |
20 Dec, 2015 |
| Expert Group Formation |
|
23 Sep, 2014 |
28 Jan, 2015 |
| JSR Review Ballot |
View results |
09 Sep, 2014 |
22 Sep, 2014 |
| JSR Review |
|
26 Aug, 2014 |
08 Sep, 2014 |
|
Status: Final
JCP version in use: 2.10
Java Specification Participation Agreement version in use: 2.0
Description:
This JSR is to develop JSF 2.3, the next release of Java Server Faces.
Expert Group Transparency:
Public Project Page
Public Communications
Issue Tracking
|
 |
Ed Burns |
Oracle |
| |
Manfred Riem |
Oracle |
 |
|
| |
Frank Caputo |
Civici, Cagatay
: Cagatay Civici |
IBM
: Paul Nicolucci |
| |
ICEsoft Technologies Inc.
: Ken Fyten |
Irian Solutions GmbH
: Leonardo Uribe |
Josh Juneau |
| |
Liferay, Inc
: Neil Griffin |
Mann, Kito D. |
Mueller, Michael
: Michael Müller |
| |
Oracle
: Ed Burns |
Oracle
: Manfred Riem |
Red Hat
: Brian Leathem |
| |
ZEEF
: Bauke Scholtz |
ZEEF
: Arjan Tijms |
|
|
| |
|
|
|
Updates to the Original JSR
The following updates have been made to the original proposal:
2015.07.14:
The schedule has been updated:
Q4 2015 Early Draft
Q1 2016 Public Review
Q3 2016 Proposed Final Draft
H1 2017 Final Release
Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification
Submitting Member: Oracle
Name of Contact Person: Edward Burns
E-Mail Address: edward.burns@oracle.com
Telephone Number: +1 407 458 0017
Fax Number: +1 407 251 0812
Specification Lead: Edward Burns, Manfred Riem
E-Mail Address: edward.burns@oracle.com, manfred.riem@oracle.com
Telephone Number: +1 407 458 0017, +1 435 225 4289
Fax Number: +1 407 251 0812, +1 314 682 0561
Initial Expert Group Membership:
Neil Griffin, Liferay
Oracle
Paul Nicolucci, IBM
PrimeTek, Cagatay Civici
Brian Leathem, RedHat
Frank Caputo, Individual
Ian Hlavats, Individual
Kito Mann, Individual
Imre Osswald, Individual
John Yeary, Individual
Arjan Tijms, Individual
Supporting this JSR:
Neil Griffin, Liferay
Oracle
Paul Nicolucci, IBM
PrimeTek, Cagatay Civici
Brian Leathem, RedHat
Frank Caputo, Individual
Ian Hlavats, Individual
Kito Mann, Individual
Imre Osswald, Individual
John Yeary, Individual
Arjan Tijms, Individual
Section 2: Request
2.1 Please describe the proposed Specification:
This JSR aims to improve the clarity of the existing JavaServer Faces (JSF) specification and introduce a small, targeted set of new features as directed by community contribution.
Requirements are grouped into four major categories: Small-scale new features, community driven improvements, and platform integration.
Small-scale new features
While the scope of new features is intentionally limited, it is important to continue to evolve JSF to support the growing needs of existing users. To that end, an enhancement to the JSF Ajax API is proposed: namely Ajax method invocation. This feature allows invoking CDI managed bean methods directly from Ajax, allowing the response to be sent using Java EE 7 standard JSON.
Community driven improvements
JSF has always been indisputably community focused. This tradition continues in JSF 2.3. While the set of issues addressed is very much up to what the expert group is willing to contribute, some obvious suggestions include multi-field validation, @Inject FacesContext, EL performance optimizations, and cross-form Ajax clarifications.
Platform integration
Previous versions of JSF intentionally lagged one version behind the Java EE version in which it was bundled. This release abandons this approach in favor of being able to leverage platform features from Java EE 8 and Java SE 8.
Support for MVC 1.0
Several existing features of JSF may make sense to expose for use by the MVC 1.0 specification, also in Java EE 8. These features may include but are not limited to: The Facelets View Declaration Language, JSF native CDI scopes, and faces flows.
2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)
This specification is targeted for Java SE 8.0 or higher and Java EE 8 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 JSR will be targeted for inclusion in the Java EE 8 platform.
2.4 What need of the Java community will be addressed by the proposed specification?
See 2.1 above.
2.5 Why isn't this need met by existing specifications?
See 2.1 above.
2.6 Please give a short description of the underlying technology or technologies:
See 2.1 above.
2.7 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)
JSF 2.3 will use the same root package name as JSF 2.2, namely javax.faces.
2.8 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?
No.
2.9 Are there any security issues that cannot be addressed by the current security model?
No.
2.10 Are there any internationalization or localization issues?
This JSR will use the I18N support in Java SE.
2.11 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?
No.
2.12 Please describe the anticipated schedule for the development of this
specification.
Q3 2014 Expert Group formed
Q1 2015 Early Draft
Q3 2015 Public Review
Q1 2016 Proposed Final Draft
Q3 2016 Final Release
2.13 Please describe the anticipated working model for the Expert Group working on developing this
specification.
The primary means of communication will be e-mail. We will solicit feedback from the community and leverage the open source development model.
2.14 Provide detailed answers to the transparency checklist, making sure to
include URLs as appropriate:
JSF 2.3 will follow the same working model as JSF 2.2.
In particular, a project site (https://javaserverfaces-spec-public.java.net/) will be used to track all issues and disseminate information on the progress of the JSR.
* Is the schedule for the JSR publicly available, current, and updated regularly?
Yes, the schedule will be available on the project page for the JSR at http:// javaserverfaces-spec-public.java.net.
* Can the public read and/or write to a wiki for the JSR?
No, we'll use a public mailing list for comments instead (users@javaserverfaces-spec-public.java.net).
* Is there a publicly accessible discussion board for the JSR that you read and respond to regularly?
The mailing lists available at https://java.net/projects/javaserverfaces-spec-public/lists.
* Have you spoken at conferences and events about the JSR recently?
Yes, extensively. Most recently at JavaLand in March 2014.
* Are you using open-source processes for the development of the RI and/or the TCK?
The Reference Implementation will be developed as part of the open source Project Mojarra (http://javaserverfaces.java.net). The final RI will be available from the download page. The TCK is not open source.
* What are the Terms of Use required to use the collaboration tools you have prepared to use with the Expert Group, so that prospective EG members can judge whether they are compatible with the JSPA?
The Java.net terms of use available at https://java.net/terms_of_use.
* What is the location of your publicly-accessible Issue list? In order to enable EC members to judge whether Issues have been adequately addressed, the list must make a clear distinction between Issues that are still open, Issues that have been deferred, and those that are closed, and must indicate the reason for any change of state.
All issues related to the specification will be tracked in the publicly accessible JSF specification project issue tracker (https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC). The issue tracker link is also accessible from the JSR project page.
* What is the mechanism for the public to provide feedback on your JSR?
The user's e-mail alias users@javaserverfaces-spec-public.net.
* Where is the publicly-accessible document archive for your Expert Group?
Also available at Java.net https://java.net/projects/javaserverfaces-spec-public/downloads.
* Does the Community tab for my JSR have links to and information about all public communication mechanisms and sites for the development of my JSR?
Yes, see https://javaserverfaces-spec-public.java.net/.
* Do you have a Twitter account or other social networking feed which people can follow for updates on your JSR?
Yes, @jsf_spec.
* Which specific areas of feedback should interested community members (such as the Adopt-a-JSR program) provide to improve the JSR (please also post this to your Community tab)?
In general, any of the areas listed in Section 2.1. For more information, refer to the Community tab in the JSR page at jcp.org.
2.15 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 reference implementation will be made available standalone and also as part of the reference implementation for the Java EE 8 platform. The TCK will be made available standalone and as part of the Java EE CTS.
2.16 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.17 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.
Specification license
RI license
- Commercial use
The RI will be available for commercial use under the
CDDL 1.1 open source license,
the GPLv2 with Classpath Exception open source license,
or this RI license.
- Non-Commercial use
The RI will be available for non-Commercial use under the CDDL 1.1 open source license
or the GPLv2 with Classpath Exception open source license.
TCK license
- Commercial use
The TCK will be available for commercial use under this TCK license.
- Non-Commercial use
As required by the Java Specification Participation Agreement (JSPA), the TCK will be licensed at no charge without support to qualified not-for-profit. The Compatibility Testing Scholarship Program will verify such qualification. Support may also be provided at no charge with approval of the scholarship board. For more information, please refer to:
http://www.oracle.com/technetwork/java/index-137188.html
2.18 Please describe the communications channel you have established for the public to observe Expert Group deliberations, provide feedback, and view archives of all Expert Group communications.
The Expert Group will conduct business on a publicly readable alias. The public will have an alias on which to provide feedback and discuss issues related to the JSR. There will also be a publicly accessible JIRA and document archive. (See also 2.19 and 2.20 below.)
2.19 What is the URL of the Issue Tracker that the public can read, and how does the public log issues in the Issue Tracker?
https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC
2.20 Please provide the location of the publicly accessible document archive you have created for the Expert Group.
https://java.net/projects/javaserverfaces-spec-public/downloads
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.
JSF 2.2 specification (https://jcp.org/en/jsr/detail?id=344).
3.2 Explanation of how these items might be used as a starting point for the work.
The JSF 2.2 specification will be the starting point for this work.
|
