Until now, most people are using the WIKI[1] for getting myfaces to work with facelets. I was wondering if we want to make MyFaces include support for facelets natively. This should be able to be done in such a way to prevent problems for those that do not use facelets.
Option 1) Add everything to tomahawk.jar including the TagHandler classes and taglib.xml file(s). This is easiest, and will not cause issues since non-facelet users will not be using those classes, and therefore if they don't have facelets in their classpath, it shouldn't matter. Option 2) Create a new myfaces jar file (tomahawk-facelets-1.1.2.jar for example) that contains only the code and configuration necessary to "plug" tomahawk into facelets. This is possibly more elegant but more of a pain to setup. Option 3) Maintain all this at jsf-comp. This works, but new users may not know about jsf-comp and it is harder to stay in sync with facelet and myfaces version changes (since it is not tied into the release cycle). Since facelets hasn't changed the taglib.xml structure at all, facelet version should not be a major issue. This would also make issues like what tree2 had a mute point since we could include component handlers built in to translate any "non-standard" logic in the Tag classes. This methodology could be applied to the sandbox as well. Once there is some code in SVN I would think myfaces developers could easily maintain their configuration for their components as well since there would be examples from other components to learn from (so even developers without facelets experience shouldn't have any issues). What do you think? -Andrew [1] http://wiki.apache.org/myfaces/Use_Facelets_with_Tomahawk
