Re: [jsr-314-open] f:event mismatch between pdf and htmls

Actually the short cuts are documented, but not in the PDF :-)

you can find them in the javadocs (they are also not entirely correct) But as it seems we got it wrong in myfaces, as soon as I get the offical answer here, what the correct attribute is (type it should be according to my info as the PDF states and nothing else), I also will file a bug within MyFaces to get this corrected for the beta. Werner On Fri, Jan 29, 2010 at 5:07 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > Hello Werner, > > please see here: > > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=712 > > Also the "short-cuts" are not documented at all. > > I should, I guess, just file another bug :-) > > -Matthias > > On Fri, Jan 29, 2010 at 4:00 PM, Werner Punz <werner.punz(a)gmail.com&gt; > wrote: > > To reply myself, I have to apologize. If I have read the html docs more > > throughly I would have noticed that both attributes still are stated > > name > > and type. > > But the question persists since the html still does not show the type > > attribute exactly > > what is the correct behavior, is it type only as stated in the pdf or > > type > > and name as stated in the html (where the type attribute ist stated but > > not > > explicitely listed as separate attribute)? > > > > > > Werner > > > > > > On Fri, Jan 29, 2010 at 3:43 PM, Werner Punz <werner.punz(a)gmail.com&gt; > > 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 > >> > > > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf