myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe" <lu4...@gmail.com>
Subject [myfaces commons] discussion about reorganization of this project is required!
Date Fri, 06 Jun 2008 13:20:59 GMT
Hi

I'll start to upgrade component from sandbox to tomahawk.

The first item on my list of todos is move this converters and validators
(first check and solve possible issues on JIRA)

s:convertBoolean
s:convertDateTime
s:convertNumber
s:validateCompareTo
s:validateCSV
s:validateISBN
s:validateUrl

Please note that long time ago this upgrade was approved, but this was not
applied due to code generation discussion.
<file:///C:/GSOC/workspace/tomahawk-compgen/oldsandbox-site/tlddoc/s/validateUrl.html>

Actually on tomahawk exists this validators:

t:validateCreditCard
t:validateEmail
t:validateEqual
t:validateRegExpr

The idea is that all this converters and validators be on myfaces-commons.
But originally tomahawk is 1.1 compatible, and there was comments about
commons should have 1.1  and 1.2 converters and validators. If this is true,
tomahawk should refer myfaces commons converters and validators on its tld,
and have dependecies to commons (if false this is valid only for 1.2).

The new unpack plugin allow us to manage this issues more easily, enforcing
just the necessary files to maintain.

In order to be consistent with this intentions my first approach would be:

1. Use this layout for myfaces-commons:

myfaces-commons-converters
myfaces-commons-converters12
myfaces-commons-validators
myfaces-commons-validators12
myfaces-commons-utils

2. Use myfaces-builder-plugin for this stuff.

3. Refer converters and validator from commons to tomahawk tld (the
intention is avoid changes on existing applications).

Suggestions are welcome

regards

Leonardo Uribe

Mime
View raw message