On 5/3/06, Michael Heinen <[EMAIL PROTECTED]> wrote:
I read the two options and I am in doubt about the following statement
regarding alias beans for my use case:
"Note also that component binding is not supported via "aliased" names.
Therefore the included page cannot include any component with a
"binding" attribute"
So I can't use something like:
<h:selectOneMenu binding="#{myController.myMenu}"/>
I have not used aliasBean since switching to facelets, so I can't
really comment on its limitations other than to say that aliasBean
does have limitations.
Currently I don't use facelets in my project but tiles.
I have read in the wiki that facelets does not correctly work with tree2
components. I am afraid of getting new problems when I add facelets.
There's no question that switching to facelets will require some
effort on your part, especially if you're using jsp rather than jspx.
However, facelets will work with tree2, although it requires either
using a tree2 component handler (which you can find on the
http://wiki.apache.org/myfaces/Use_Facelets_with_Tomahawk wiki page)
or requires using the fully-qualified internal attribute names).
Sean has rewriting the tree2 attribute handling on his todo list, and
even this workaround won't be necessary in the long run.
In my opinion, the short time I spent making the transition to
facelets was worthwhile.
As far as I know, there are no outstanding problems between the latest
versions of facelets and MyFaces/Tomahawk 1.1.2 and beyond.
