On 8/2/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> If we design our MyFaces components right, the only component classes
> that will need facelets tag handlers are those with method bindings.
> The method binding method signature for an attribute has be specified
> in a facelets component tag handler.
Well lets make sure we do this part whenever possible. It might take
a little time but I'd like to minimize the need to add extra facelets
specific stuff. But, when its unavoidable, I agree with Matthias'
suggetsion of o.a.t.facelets
For most of the remaining problem components, it's simply a matter of
taking care of the generic attributes and making them explicit html
attributes like you did for tree2.
The only component I know to be more complicated than fixing
attributes (in MyFaces) or defining method bindings (in facelets tag
handlers) is t:tree. The jsp tag and the component don't use the
same attributes.
Lets create improvement issues in JIRA for each of the tomahawk
components that don't support facelets out of the box. We can then
assign them to ourselves if we have time to work on them.
Sounds good. That's what I was planning on doing once someone else
got the maven foundation in place.
By the way, I came across the facelets maven location earlier:
http://wiki.java.net/bin/view/Projects/FaceletsFAQ#Is_Facelets_in_ibiblio_or_anothe
I have one in mind since I need it for a demo app I'm writing
(t:popup.) Lets just be sure to check JIRA and assign to ourselves so
we don't duplicate effort.
Don't need to do anything for t:popup -- at least the following is
working fine for me.
<tag>
<tag-name>popup</tag-name>
<component>
<component-type>org.apache.myfaces.HtmlPopup</component-type>
<renderer-type>org.apache.myfaces.Popup</renderer-type>
</component>
</tag>
