myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno Aranda" <>
Subject Re: Commons Jsf Utils
Date Fri, 24 Nov 2006 10:17:26 GMT
It seems a good idea to me. But should this commons lib be jsf version
independent (I mean, same jar to be used in jsf 1.1 and jsf 1.2 or
not). There are classes, like UIComponentTagUtils, which would have a
different implementation for jsf 1.1 and 1.2, but there are other
(many) classes that can work for 1.1 and 1.2 out of the box. I would
say it would be better to have a unique implementation of
myfaces-commons and it should be jsf version independent...



On 24/11/06, Manfred Geiler <> wrote:
> Hi *,
> Anyone remembering the old idea of having a separate "commons jsf
> utils" project?
> Mission:
> - provide utilities for JSF component developers as well as JSF
> application developers
> - provide a stable API
> - must not depend on a certain JSF implementation
> - own release schedule independent of core and tomahawk. Maybe
> propelled by a sister project of course... ;-)
> One perfect example of a jsf-commons class I just stumbled across is
> UIComponentTagUtils. It's the class where all those boring
> set*Property methods are implemented, that do the "if value-binding
> then... else..." things.
> Proposal:
> - Initiate a new MyFaces sub-project called "commons-jsf"
> (Yes! There did exist a "commons" in ancient times. It was the
> forerunner for our current "shared" project and the reason we renamed
> "commons" to "shared" was, that we planned to create a REAL commons
> project later. Remember?)
> - We start with those obvious common jsf utils (like UIComponentTagUtils)
> - Each (new) util class must be carefully designed to be able to
> provide a robust API
> Thoughts?
> Manfred

View raw message