myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Kienenberger" <>
Subject Re: [TOMAHAWK] Facelets support was (RE: [Solved] Unable to display Suggested Items using Sandbox component s:inputAjaxSuggest)
Date Tue, 27 Feb 2007 17:41:14 GMT
As always, it's not a matter of do we want it, it's a matter of who's
going to do it, and how.
For there to be any integrated solution, it has to be a complete
solution since it is my understanding that it is not possible to
override whatever facelet tags we define.   Thus, we probably will
need to code-generate the taglib.xml files in order to keep them
up-to-date since the person working on a particular component may not
realize they need to change the facelets portion of the component

It would be good if the facelets support were in a separate maven
module so that the main Tomahawk code does not depend upon facelets.

What you propose sounds great -- when will you provide patches to
implement it? :-)

On 2/27/07, Beelen, Marco <> wrote:
> It appairs that some additional code is required to use at least one
> tomahawk component in combination with facelets. As always there can be
> discussion about whom should provide support for this kind of code (the
> facelets or tomahawk community)
> As being a user I would like to gets such 'integration'-code along with the
> component.
> On the other hand I would understand if the myfaces-community would not like
> to have some code dependand on com.sun.facelets.tag.*-classes in the
> tomahawk-project.
> How do you feel about a creating seperate project
> groupId=org.apache.myfaces.tomahawk and artifactId=tomahawk-facelets, which
> has dependancies on org.apache.myfaces.tomahawk:tomahawk and
> com.sun.facelets:jsf-facelets and contains the necessary code to get all the
> tomahawk components working in a facelets-based application?
> That way the user only needs to include 1 dependancy and the codebases stay
> clean?

View raw message