I was thinking that instead of displaying alert, the messages would appear in the same place as they do in server-side. So keep the existing javascript validator/converter stuff but change where/how it is displayed. We'd probably have to render a hidden container for each field, which the javascript would populate and make visible.
Taking this route over a dialog means we could also probably provide some kind of on-tab-out instant validation for more data-entry heavy applications. That said these approaches are not mutually exclusive. Danny On 2/28/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
are you talking about still using JS for the client side converter/validator stuff, but just don't use alert(), instead using a "web2.0-ish" dialog ? The validator/converter stuff isn't just an alert(). We have "client side" Converter (with getAsObject/String) and Validators (with validate) and FacesMessage etc. Here is more on that interesting topic: http://incubator.apache.org/adffaces/devguide/clientValidation.html -Matthias On 2/28/07, Danny Robinson <[EMAIL PROTECTED]> wrote: > Guys, > > Would there be support for an enhancement to the client-side validation so > that it behaves in the same way as the server-side logic? Meaning, we'd get > rid of the javascript alert dialog and instead dyanamically show/hide the > error messages in the page. > > If so, I'll raise a JIRA issue and look into possible solutions. Tips & > suggestions welcome. > > Danny > > -- > Chordiant Software Inc. > www.chordiant.com > -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
-- Chordiant Software Inc. www.chordiant.com
