I'm pleased to announce another revision of the Java EE Web Tier. In Jan Luehe's blog you can find out what's new in JSP 2.1 Proposed Final Draft 2 (PFD2). The Change Log for Servlet 2.5 will give you the scoop on the Servlet spec. This blog entry will show what's new in the JSF spec.
In JSF, the most visible new feature since the last draft of the spec is the addition of the
invokeOnComponent() method on
UIComponent. See below for more details.
Spec changes since PFD, chronologically by section number
3.1.10: Specify how EL
ValueExpressionsmust me handled in the attributes map returned from
5.4: List the supported Java EE 5 annotations one may put in a JSF Managed bean.
@Resource @Resources @EJB @EJBs @WebServiceRef @WebServiceRefs @PersistenceContext @PersistenceContexts @PersistenceUnit @PersistenceUnits
2.2.2: Define the term "local value" more concretely.
Preface: Added section on backwards compatibility with previous versions of the JSF spec.
9.4.8: Explicitly state that the use and meaning of a
UIParameterchild is the responsibility of the parent component inside which it is nested.
5.3: State that managed bean properties may be Java enum types. Define coercion rules.
7.1.1: Widen the expected type returned from a
UICommandaction method to be
String. This allows the use of Java enum types as returns from action methods, which can simplify navigation rules.
7.3: State that the Action method must return
3.1.8: New method:
UIComponent.invokeOnComponent(), and supporting callback interface
ContextCallback. This method allows you to execute a callback on an arbitrary node in the view given its
clientId. An override is provided for
UIDatathat provides for correctly positioning the table to the proper row before continuing to find the component.
126.96.36.199: Add a note mentioning that
tld-versionin an explicit taglib def, and
versionin an implicit taglib def are semantically equivalent with respect to their use in determining the backwards compatability strategy employed.
JSF-API Contract Changes, chronological by functional area
Standard HTML RenderKit: Changes to outputText, outputFormat, message and messages renderers. Add header and footer facets to the declaration of
UIColumn. Specify that the default value of the "rendered" property is
true. The "target" attribute of the link renderers is not a passthru attribute. Modify commandLink renderer to describe what should happen if "disabled" is true. Attributes that have a boolean value or meaning, such as "ismap", "disabled", or "readonly", must be rendered without attribute minization. For example, "ismap=ismap". Update "acceptcharset" attribute on Form to be non-passthrough since the attribute value is rendered as "accept-charset". GridRenderer supports the "caption" attribute.
Relax the spec language for
findComponentto allow for any implementation that accomplishes the same thing as the specified algorithm. Also allow for
findComponentto work properly if nested naming containers with the same name exist.
JSF-API Implementation Changes, chronological by functional area
Refactored build system to be more maintainable.
Rob Gibson contributed a fix to improve how more than one JSF portlet may run in the same portal.
Performance improvements in attribute/property transparency.
FacesServletso that if the servlet is prefix mapped, requests starting with
Changes to make tree creation and content interweaving work with
@exceptionjavadoc statements to
@throwsstatements due to Sun bug 6359046.
UIParameterchildren inside of select* components.
Various backwards compatibility allowances.