Java News from Friday, September 19, 2008

Sun has posted an early draft review of Java Specification Request 314: JavaServer Faces 2.0. This makes various minor updates to support Java 1.5 features, align the spec with JAX-RPC 2.0, and support subsitution groups. According to the JSR:

Requirements are grouped into four major categories: Ease of Development, New Features and Fixes, Performance, Technology Adoption. Following are some initial requirements that will be prioritized and considered when the Expert Group convenes. Not all of these ideas will be in the final specification. Some of these requirements may be met in the Servlet specification (or other Java EE specification) but they are stated here because they are critical to the success of JavaServer Faces.

Ease of Development

While this was the major theme for Java EE 5, it was not the major theme for the version of the JavaServer Faces specification included therein. The act of writing JSF applications and components "by hand" will be made much easier by this JSR. Example requirements in this category include:

There are also a number of container improvements that should be considered to improve developing web applications in general:

New Features

Requirements in this category stem from feedback from real world JSF users and are incremental improvements on the existing specification. This category includes fixes and updates to existing APIs. Example requirements in this category include:

Runtime Performance and Scalability

The flexibility of the JavaServer framework can lead to performance concerns. Requirements in this category make modifications and restrictions to the specification to increase performance across the board for all implementations of the specification. Example requirements in this category include:


Increasing the capability of the JavaServer Faces standard will continue to attract more people to write applications targeting the standard, thereby raising the bar for Java web applications. Features in this category aim to attract new developers to use products that implement the JavaServer Faces specification. Example requirements in this category include:

I've paid essentially no attention to JavaServer faces, but looking at the list of improvements for 2.0 what I'm struck by is how badly wrong they got version 1.0. I mean, they're just figuring out that GET and bookmarkable pages are a good idea now in 2008? Comments are due by October 16.