Hi!
Mario, you are not alone in hating the shared concept. ;-)
Good!
1) has a super stable API
That is true, that might be the hardest part.
2) is used (ie. shared) by the myfaces core(!) as well as other myfaces
projects
Sure!
3) may be used by the experienced JSF app
Problem here again is the name of such a lib:
myfaces-commons-base?
myfaces-commons-core?
myfaces-commons-super?
myfaces-commons-commons? ;-)
I'd opt for myfaces-base, but to say the truth, I do not care about the
name, whatever name it has will be good for me as long as
Hi,
2008/4/2, Matthias Wessendorf [EMAIL PROTECTED]:
Problem here again is the name of such a lib:
myfaces-commons-base?
myfaces-commons-core?
myfaces-commons-super?
myfaces-commons-commons? ;-)
I'd opt for myfaces-base, but to say the truth, I do not care about
we already have a very raw starting point in the current commons,
not yet finished, but it's there ;-)
The started commons-(converters|validators) are IMHO a other type of commons,
not for use in jsf-impl classes but for application developper. This
is for nice and convenient utils
