[
https://issues.apache.org/jira/browse/BVAL-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870098#action_12870098
]
Mark Struberg commented on BVAL-1:
----------------------------------
> Why would we move these out?
because the standard JSR-303 API will most probably be provided by the
container (e.g. geronimo). So any non-standard validation must not be part of
this package.
Because, if you code your application and like to use the @Email (which is not
part of the JSR-303 standard API afaik), then you would end up with not being
portable.
But if we split this additional functionality into an own api/impl jar (or a
single 'extensions-impl.jar') then we would be perfectly portable. I assume
that this 'extension-impl' only uses portable JSR-303 functions and will also
run on other 303 implementations like Hibernate Validator.
> split usable validations like @Emain from our impl
> --------------------------------------------------
>
> Key: BVAL-1
> URL: https://issues.apache.org/jira/browse/BVAL-1
> Project: BeanValidation
> Issue Type: Improvement
> Reporter: Mark Struberg
> Assignee: Mark Struberg
>
> Currently there are a few very useful Validations included in the impl.
> Since they are in fact independent of the actual JSR-303 implementation, we
> should split them out into two own modules
> * validators-api which contains only the annotations and public stuff
> * validators-impl which contains the implementation stuff which are not
> needed at compile time (always used with <scope>runtime</scope>)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
