Title: Java Platform, Enterprise Edition 8 (Java EE 8) Specification Summary/Description: This JSR is to develop Java EE 8, the next release of the Java Platform, Enterprise Edition. Duration: 2 weeks Section 1: Identification Specification Lead: Linda DeMichiel E-Mail Address: linda.demichiel@oracle.com Telephone Number: +1 408 276 7057 Specification Lead: Bill Shannon E-Mail Address: bill.shannon@oracle.com Telephone Number: +1 408 276 7280 Initial Group Membership: TBD Supporting this JSR: TBD Section 2: Request 2.1 Please describe the proposed Specification: This JSR is to develop Java EE 8, the next release of the Java Platform, Enterprise Edition. The main focus of this release is on support for HTML5 and the emerging HTTP 2.0 standard; enhanced simplification and managed bean integration; and improved infrastructure for applications running in the cloud. Since its inception, the Java EE platform has been targeted at offloading the developer from common infrastructure tasks through its container-based model and abstraction of resource access. In recent releases the platform has considerably simplified the APIs for access to container services while broadening the range of the services available. In this release we aim to continue the direction of improved simplification, while extending the range of the Java EE platform to encompass emerging technologies in the web space and in cloud technology. - Latest web standards - Java EE 7 delivered support for HTML5 dynamic and scalable applications with the Java API for WebSocket, the JSON Processing API, and Servlet NIO. Web standards continue to evolve, and it is critical that the Java EE platform support developments in this space. In Java EE 8 we expect to augment our support for HTML5 applications by adding support for server-sent events, standardized binding between JSON text and Java objects, and improvements to the Java API for WebSocket and the Java API for JSON Processing. We expect to add support for the emerging HTTP 2.0 standard (scheduled for submission as a Proposed Standard in 2014) to the Servlet API. We will also consider the addition of support for JAX-RS action-based MVC. - Ease of development - We plan to enhance the managed bean model to make ease of use features that are currently available only to selected components available to all managed beans via the mechanisms provided by CDI. In particular, we plan to consider enhancements for declarative security by means of CDI interceptors and for notifications for timed events by means of the CDI event and observer mechanism. - Infrastructure for cloud support - We expect to augment the infrastructure added in Java EE 7 for cloud support. Areas that we plan to consider include support for configuration of multiple tenants; simplified and improved security configuration; and REST-based APIs for monitoring and management. - Alignment with Java SE 8 - Java EE 8 will build on Java SE 8. We will encourage component JSRs to review and improve their APIs with the Java SE 8 language changes in mind, so that developers will be able to take advantage of new features such as repeating annotations, lambda expressions, the Date/Time API, type annotations, Completable Futures, etc. - Preliminary contents - We expect that the following new JSRs will be candidates for inclusion in the Java EE 8 platform: JCache (JSR-107) Java API for JSON Binding (JSR-TBD) Java Configuration (JSR-TBD) The new component JSRs that we plan to propose for inclusion add significant capabilities to the platform: JCache enables scaling of applications by standardizing a powerful caching layer accessible from all containers; the API for JSON Binding builds on the API for JSON Processing to provide for mapping between JSON text and Java objects; Java Configuration provides a standard mechanism for specifying, packaging, and accessing configured resources and properties independent of the application that may require or use them. Several of the technologies already included in the Java EE platform are expected to be updated for the Java EE 8 release, including all or some of the following: Java API for WebSocket Java API for JSON Processing (JSON-P) Java API for RESTful Web Services (JAX-RS) JavaServer Faces (JSF) Servlet Expression Language (EL) Interceptors Java Messaging Service (JMS) Concurrency Utilities for Java EE Batch Applications for the Java Platform Contexts and Dependency Injection for Java EE (CDI) Bean Validation Common Annotations Java Connector Architecture Java Transaction API (JTA) Java Persistence API (JPA) Enterprise JavaBeans (EJB) JavaServer Pages (JSP) - Web Profile - This JSR will also update the Java Enterprise Edition Web Profile to version 8. In addition to incorporating the latest version of the technologies currently in the Web Profile, we expect to consider adding new required technologies to the Web Profile, such as the new API for JSON Binding. - Pruning - In accordance with the pruning process defined by the Java EE 6 specification, we will consider designating the following as Proposed Optional in this release: the EJB 2.x client view APIs (EJBObject, EJBHome, EJBLocalObject, EJBLocalHome) and support for CORBA IIOP interoperability. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.) This specification defines a release of the Java EE 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. This JSR updates the Java EE platform and the Java EE Web Profile. 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: A detailed description of Java EE functionality can be found in the Java EE Specification, see http://jcp.org/en/jsr/detail?id=342. 2.7 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.) The Java EE platform itself does not require a package name. All of its requirements are reflected in the packages of its constituent Java APIs. 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? Java EE 8 addresses mechanisms and policies required for secure usage of its constituent component models and access APIs. These mechanisms must be compatible with the security facilities of Java SE 8. Java EE 8 may define additional Service Provider Interfaces, including those that allow security technology vendors to integrate with Java EE application servers. 2.10 Are there any internationalization or localization issues? Java EE uses the I18N support in Java SE and defined in constituent technologies. 2.11 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work? Other than the Java EE specification itself, the Java EE Web Profile specification and the new versions of their constituent components, Java EE 8 should not require other existing specifications to be revised. 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 Q4 2015 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 email, with conference calls and face-to-face meetings scheduled as needed. 2.14 Provide detailed answers to the transparency checklist, making sure to include URLs as appropriate: The javaee-spec.java.net project site will be used to track all issues and disseminate information on the progress of the JSR. - 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, if 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 will use a public mailing list for comments and discussion. - I read and respond to posts on the discussion board for my JSR on jcp.org. We will 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. Yes, most recently at JavaOne. - 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 the GlassFish open source application server, see http://glassfish.java.net/. - 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.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 RI and TCK for Java EE 8 and the Java EE 8 Web Profile will be delivered in the same way they were delivered for Java EE 7. 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 the full text of the licenses that will apply to your Final Release Specification, Reference Implementation, and Technology Compatibility Kit, or provide links to the same. TBD. No changes are expected from previous release. 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/JAVAEE_SPEC 2.20 Please provide the location of the publicly accessible document archive you have created for the Expert Group. https://java.net/projects/javaee-spec/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. Java Platform, Enterprise Edition Specification Version 7 and Java Platform, Enterprise Edition Web Profile Specification, Version 7: http://jcp.org/en/jsr/detail?id=342. 3.2 Explanation of how these items might be used as a starting point for the work. These specifications will be the starting point for this work.