jsr372-experts@javaserverfaces-spec-public.java.net

[jsr372-experts] Re: [jsr372-experts mirror] Re: Re: Re: JSF_SPEC-1 Multi-field validation proposal

From: Kito Mann <kito.mann_at_virtua.com>
Date: Fri, 13 Nov 2015 09:47:27 -0500

Fair enough :-).

On Tue, Nov 10, 2015 at 10:15 AM, arjan tijms <arjan.tijms_at_gmail.com> wrote:

> Hi,
>
> On Tue, Nov 10, 2015 at 3:34 PM, Kito Mann <kito.mann_at_virtua.com> wrote:
>
>> While we're on the subject, is there a way to provide a handler to do the
>> actual validation instead of handling it via Bean Validation? So basically
>> the method would just get a reference to all of the validation constraints?
>>
>> I know there is strong interest in using Bean Validation for all new
>> cases, but to be quite honest, many of my clients don't use it. We really
>> should have proper hooks for alternative methods (sometimes validation is
>> handled completely in the back-end, perhaps driven by a rules engine).
>>
>
> In a Bean Validation validator (an implementation of ConstraintValidator)
> you can handle validation in whatever way you'd like. So if you want to
> completely delegate the validation to the backend you can of course do so.
> In a way, it's not that different from the JSF Validator interface, except
> that it's more advanced.
>
> If we'd provide our own handler wouldn't we just be duplicating the
> existing ConstraintValidator interface?
>
> Kind regards,
> Arjan Tijms
>
>
>
>
>>
>> ___
>>
>> Kito D. Mann | @kito99 | Author, JSF in Action
>> Web Components/Polymer, JSF/Java EE, and Liferay training and consulting
>> Virtua, Inc. | http://www.virtua.com |
>> http://www.JSFCentral.com | @jsfcentral
>> +1 203-998-0403
>>
>> * Upcoming JavaOne 2015 talks on JSF, MVC, and Web Components:
>> http://bit.ly/1jvLRse
>> * Listen to the Enterprise Java Newscast: *http://
>> <http://blogs.jsfcentral.com/JSFNewscast/>enterprisejavanews.com
>> <http://ww.enterprisejavanews.com>*
>>
>>
>> On Mon, Nov 9, 2015 at 4:32 PM, Edward Burns <edward.burns_at_oracle.com>
>> wrote:
>>
>>> On Fri, Sep 25, 2015 at 9:40 AM, Frank Caputo <frank_at_frankcaputo.de>
>>> wrote:
>>>
>>> FC> - There are different methods to create the copy of the bean, but
>>> FC> dont we need a deep clone in all cases?
>>>
>>> >>>>> On Fri, 25 Sep 2015 10:38:15 +0200, arjan tijms <
>>> arjan.tijms_at_gmail.com> said:
>>>
>>> AT> Not really. [...]
>>>
>>> I wanted to share one additional point of feedback from my JavaOne
>>> co-speaker Lars Bilger at Lufthansa systems. Lars suggested we add an
>>> option to disable the copy and just populate the bean eagerly. This
>>> seems like a fine option to me.
>>>
>>> Ed
>>>
>>> --
>>> | edward.burns_at_oracle.com | office: +1 407 458 0017
>>> | 5 Business days til DOAG 2015
>>>
>>
>>
>