[ http://issues.apache.org/jira/browse/MYFACES-698?page=comments#action_12331912 ]
Mike Kienenberger commented on MYFACES-698: ------------------------------------------- I disagree. For the most part, simply supplying a META-INF\tomahawk.taglib.xml and META-INF\sandbox.taglib.xml file is sufficient. I'd love to see this happen. Such a file is being created piecemeal as facelets users use various components at http://wiki.apache.org/myfaces/Use_Facelets_with_Tomahawk For some components (I suspect that t:tree is such a component), it probably be better to clean up the Tag/Component attribute-mangling interactions so that the interface between the tag and component are cleaner. This will not only help facelets, but all other alternate viewhandlers. Once this is done, it's just a matter of adding another taglib.xml entry. Other components, like sandbox:graphicImageDynamic and t:jsValueChangeListener, are going to require Facelet TagHandlers. I'd also like to see these things added to Tomahawk and Sandbox, but it's unreasonable to expect MyFaces committers to implement these for you. I don't think it's unreasonable to allow facelet users provide such as patches and have them become part of MyFaces. I haven't looked at NavigationMenuItem, but you should either provide a patch to t:navigationMenuItem that cleans up the interaction between the tag and component or you should provide a TagHandler (actually a ComponentHandler subclass) to deal with complex interaction behavior. If you create a component handler, let me know. I'd like to collect all of these supporting java classes in one place until such time they're available as part of MyFaces. (Probably in the sourceforge jsf-comp since that's the purpose of the project). > Add facelets support for all Tomahawk components > ------------------------------------------------ > > Key: MYFACES-698 > URL: http://issues.apache.org/jira/browse/MYFACES-698 > Project: MyFaces > Type: New Feature > Components: Tomahawk > Reporter: Erik-Berndt Scheper > > Since facelets are cool :-) it would be nice to have facelet-support for all > Tomahawk components, including those which are non standard (such as the Tree > component and NavigationMenuItem (see MYFACES-697)) > This would require the following > -a java source supporting all Tomahawk components > based on com.sun.facelets.tag.jsf.html.HtmlLibrary.java in the jsf-facelets > distribution > This makes it possible to port the non-standard property usage in various > myfaces components to facelets > -an xml-file in the META-INF directory containing the facelet taglibrary. > (such as META-INF\tomahawk.taglib.xml) > This could be based on META-INF\jsf-html.taglib.xml in the jsf-facelets > distribution > This looks like a simpler (and better) approach than adapting each individual > component to work with facelets. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
