myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Wessendorf <mat...@apache.org>
Subject Re: [JSF 2.0] JSR 303 support in MyFaces 2.0
Date Tue, 20 Oct 2009 04:41:17 GMT
I think the question is why there isn't a helper like
BeanValidation.isBeanValidation() specified ?
Implementation could be somewhat similar to what MyFaces
does today. But I wonder why this wasn't done...

-M

On Mon, Oct 19, 2009 at 9:14 PM, Matthias Wessendorf <matzew@apache.org> wrote:
> Hi,
>
> in order to work on Trinidad 2.0 and 303 support (yeah need to check
> what Gerhard did for extVal) I
> took a quick look at the UIInput.
>
> I noticed a few lines containing a call like this:
>
> => BeanValidator.isAvailable
>
> This is a public field which is only there in MyFaces, not in the JSF
> 2.0 API ([1]).
>
> I know that the entire handling of checking if there is a JSR 303
> implementation is
> a little bit ugly, but I am not sure if we should introduce such a
> "public" field to the
> BeanValidator validator class.
>
> => wouldn't be good if extensions would start to rely on this field; I
> guess not there on the RI ;-)
> => does this violate the TCK ? Or would it be ? I am not sure here
> two, as it is a public field
>
> Maybe we should make the make the check become a private thing ?
>
> -Matthias
>
>
> [1] http://java.sun.com/javaee/javaserverfaces/2.0/docs/api/index.html
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Mime
View raw message