On Fri, Jan 29, 2010 at 3:43 PM, Werner Punz <werner.punz@gmail.com> wrote:

Hello Everyone

Because I was running into this issue while programming a demo application, I ran into a spec errata and am not sure what the correct behavior is.

Spec 3.4.3.4 for f:event states

The type attribute specifies the type of event, and can be any of the specification-defined events or one of any userdefined
events, but must be a ComponentSystemEvent, using either the short-hand name for the event or the fullyqualified
class name (e.g., com.foo.app.event.CustomEvent). If the event can not be found, a
FacesException listing the offending event type will be thrown. Please see the tlddocs for the <f:event /> tag
for the normative specification of the declarative event feature.

Now if we look at the corresponding html documentation:
pdldocs/facelets/f/event.html

name javax.el.ValueExpression
(must evaluate to java.lang.String) Name of the event for which to install a listener. The following table lists the valid values for this attribute, and the corresponding event type for which the listener action is registered. ...

In addition to these values, the fully qualified class name of any java class that extends javax.faces.event.ComponentSystemEvent may be used as the value of the "type" attribute.

Also, the @javax.faces.event.NamedEvent annotation may be attached to any java class that extends javax.faces.event.ComponentSystemEvent. This enables that event to be referenced from this attribute, as descibed in the javadocs for @NamedEvent.

so my final question regarding this, is the attribute type now name or type?

Werner