Making configuration options dynamic, eliminate tag handler class even for non-composite JSP components, introduce shorthand URLs for Facelet Tag Libraries, make cc:interface in composite components optional, enhance deployment, integrate with CDI
Component identification and Ajax
Support implementation of Portlet Bridge 2.0
Support for HTML5 features, such as Forms, Heading, Metadata and Section content model, Flow management, Listener for page navigation events, and new components like FileUpload and BackButton
In-process caching of Java objects allows an efficient implementation and removes the programmer from the burden of implementing cache expiration, mutual exclusion, spooling, and cache consistency. Objects type, which can be known only at runtime, can be cached, but those which implement the serializable interface can only be spooled. Package: javax.cache.
Cloud Ready Because of Container-based Model
The main focus of Java EE 7 is the cloud. The Java EE platform is already suited for cloud environment, owing to its container-based model and the abstraction of its resource access. Java EE always has been a managed environment where access to external resources and the system is controlled by the containers. The advantage of this container-based model is that portable applications can target single machines as well as cluster deployment without fundamental changes in the programming model. Java EE 7 is expected to evolve this paradigm and enhance it with some incremental changes. The interesting enhancement to look for is on how much it can leverage current architecture to support Java EE platform as a service. However, the promised enhancement under the umbrella of Java EE 7 will definitely have some operational impact on the arena of cloud computing.