commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Resolved] (VALIDATOR-219) New display method for client validation error
Date Wed, 07 Jan 2015 00:01:35 GMT


Sebb resolved VALIDATOR-219.
    Resolution: Won't Fix

Javascript routines are no longer maintained and have been deprecated

> New display method for client validation error
> ----------------------------------------------
>                 Key: VALIDATOR-219
>                 URL:
>             Project: Commons Validator
>          Issue Type: New Feature
>          Components: JavaScript
>            Reporter: Joost Schouten
>            Priority: Minor
> Hi,
> I would like to suggest to make an enhancement to the client side validation process
so that the client validation error message is displayed the same way the client side validation
messages are displayed. Personally I would prefer making this the default behavour and eliminating
the JavaScript alert(). Another option might be to change the value passed through to the
client attribute of the s:commonsValidator tag to multiple options like "alert" and "message".
> When message would be chosen, the JavaScript will populate the <div> representing
the h:message tag.
> I think this will result in a more elegant notification to the enduser.
> example:
> --------------------------
> <h:inputText id="email" value="#{}">
> 		<s:commonsValidator type="required" message="#{labels['err.requiredField']}" server="true"
> </h:inputText>
> <h:message for="email" styleClass="error"/>
> --------------------------
> We currently have a fairly elaborate system in place where empty JavaScript Array's are
generated for each validator type. Whenever a value needs to be validated, the input object
will be added to the specific validator Array. On submit each array will be checked for their
correct values , messages are dysplayed acoringly and the request is stopped.
> How do you think we should implement this feature, and what part of this process belongs
in Shale, and what part belongs in the commons validator. I also posted this RFE in the shale
issue tracker (SHALE-373).
> Thank you,
> Joost 

This message was sent by Atlassian JIRA

View raw message