For example, I believe that UpdateActionListener is not yet defined in tomahawk.taglib.xml because the JSP Tag for that component has some special logic.
Facelets now provides the <f:setPropertyActionListener> component (back-ported from JSF 1.2), so you really don't need UpdateActionListener in Facelets, afaik.
Adam Brod
Product Development Team
| "Mike Kienenberger"
<[EMAIL PROTECTED]>
06/30/2006 04:18 PM
|
|
On 6/30/06, Todd Patrick <[EMAIL PROTECTED]> wrote:
> Therefore, do I just copy the example content on the
> http://wiki.apache.org/myfaces/Use_Facelets_with_Tomahawk into my
> tomahawk.taglib.xml?
Yep.
> What does the following statement mean?
>
> "Please add additional component definitions to this example as you use
> them (in alphabetical order). To find the component and renderer types,
> look at the getComponentType() and getRendererType() methods in the Tag
> class for the component. If the Tag class does anything other than
> providing pass-through getters and setters, you will need to write a
> facelets TagHandler or submit patches to MyFaces to "standardize" the
> tag handler."
When I started the page, there were no taglib definitions. As
people have used the various tomahawk components, they've added new
definitions for each component to the page. I suspect we're getting
closer to the point where we have everything defined. The above
statements are instructions on how to create a new entry for a missing
component.
Disclaimer: This electronic mail and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify the sender immediately by replying to this email, and destroy all copies of this email and any attachments. Thank you.
