On Mon, November 6, 2006 12:24 pm, Rene Gielen wrote:
> Right now this switch already present. DWR is utilized for that, not
> depending on which AJAX UI framework is used - so if we would add
> sciptaculous support or such, we would not need to change the remoting
> based validation solution.
>
> WW2 already had support for JS client side validation, but the trouble
> is that you always have to code two different validation logics (Java /
> Expression language vs. JavaScript) for one validation. The current
> solution using DWR utilizes the full server side validation framework,
> by that having one single source for definition and/or custom
> implementations of validators, both for full request (classic) server
> side validation and "client side style" validation on focus changes in
> the webform, using half requests via DWR.

Cool, I wasn't aware of that.  I suppose some could have a problem with
DWR being used... I'm not one of them, I'm quite a big fan of DWR :) ...
but the core concept is absolute a good one.

> To be honest, I would not want to miss this any more ;)

Hehe, me neither... ironically, my current project still uses S1, and I
wrote some code to call Commons Validator on the server via AJAX, so we
use the exact same validations for the "client-side" validations as the
server-side ones.  Works really nice, and like you say, it's very nice
having the validation definitions (and logic, since we have quite a few
custom validators) all in one place.

> Regards,
> Rene

Frank


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to