+1 to not naming it validations. There is already a commons validator.
-0 to including core in the name
Strong -1 to including JSR in the project name. A jar is nearly an
enhancement number for java. You wouln't name your project something
like MyFaces-1234 after a Jira ticket number.
On Apr 26, 2008, at 10:25 AM, "Gerhard Petracek" <[EMAIL PROTECTED]
> wrote:
hello alexander,
i got your idea.
however, i hope we will find a short and fancy name.
if we don't have 'core' within the name, i think we have to find
something else than just 'validation'.
otherwise it will be a bit confusing for users due to the fact that
the core itself doesn't validate.
concrete validation logic is located within the independent/optional
modules.
the target is to have a core which provides the infrastructure and
which encapsulates the specifics of the jsf version. furthermore,
the core is independent of specific annotations. the optional
modules provide the concrete annotations and/or validation logic
(independent of the jsf version).
(reason for and/or: we don't provide the annotations of jpa nor of
jsr 303 - we just provide the validation strategies for these
external annotations.)
@myfaces-commons-validation-annotations:
it isn't a pure annotation module - it also provides the validation
strategies and much more.
(in the case of the jpa validation support it just provides the
validation strategy.)
moreover, i would suggest that we rename seven-validation to seven-
ext-validation or a bit shorter: seven-extval (for extended
validation)
or something similar which indicates that these are our annotations
(and so on).
@myfaces-commons-validation-jsr303:
i'm fine with both jsr303 (my original suggestion) or bean-validation
the names of our compromise so far:
myfaces-commons-[new name]
(= the core)
myfaces-commons-[new name]-validation
(= our annotations + validation strategies incl. cross-component
validation infrastructure and also the jpa validation strategy,...)
myfaces-commons-[new name]-bean-validation
(= the infrastructure and validation strategies to support jsr 303)
fancy suggestions for [new name] are welcome.
(we need some suggestions to open a vote.)
or what's about something different
it isn't my favourite - however, it might be an impulse for other
suggestions.
e.g.:
myfaces-commons-validation-core
myfaces-commons-validation-extval
myfaces-commons-validation-jsr303 (or bean-validation)
(i prefer an independent name.)
regards,
gerhard
2008/4/25 Jesse Alexander (KSFH 336) <[EMAIL PROTECTED]
>:
we are getting side-tracked...
let's find a name within this thread! :)
validation ?
->
myfaces-commons-validation
myfaces-commons-validation-annotations (was -validation)
myfaces-commons-validation-jsr303 (was bean-validation)
kind regards
Alexander
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
