Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Message-ID: <16650073.1184112185454.JavaMail.jira@brutus>
Date: Tue, 10 Jul 2007 17:03:05 -0700 (PDT)
From: "Paul Benedict (JIRA)" <jira@apache.org>
To: commons-dev@jakarta.apache.org
Subject: [jira] Commented: (VALIDATOR-232) Add script attribute to control
 script generation
In-Reply-To: <29432383.1183869725106.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/VALIDATOR-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511613 ] 

Paul Benedict commented on VALIDATOR-232:
-----------------------------------------

I don't use any javascript validation on my apps because, specifically, I do not want to expose any mask elements. In a perfect world, I could switch off validation scripting for these fields -- not just password fields -- on an as-needed basis. But because I don't have this freedom, I only do server side validation. And if I had this option, I may find in the future how useful this is for other things... 

You raise a good point about switching off validations per type or substituting corrected scripts. However, you'd be surprise how many good java developers do not know javascript :-) In some instances, a person may simply just choose to turn it off rather than replace it.

I've been viewing this issue to something like CSS stylesheets. With the CSS "media" attribute, and I get to say which media the styling belongs (screen, printer, audio, etc.). Likewise, I believe it is good to give developers the freedom to direct what media the validation belongs. For Commons Validator, there's two media components: scripting and Java. If I don't care for how a script works, I'd be more willing to disable it and rely on the server-side version than replace it.

While I haven't done this yet, I'd be very interested in replacing some client-side validation with perhaps DOJO/Ajax validation. I may want to (1) have only one form field that uses Web 2.0 features, (2) keep the standard JS validation on other fields but (3) still rely on the server-side validation for all fields as "standard practice". It opens up some interesting possibilities here.

> Add script attribute to control script generation
> -------------------------------------------------
>
>                 Key: VALIDATOR-232
>                 URL: https://issues.apache.org/jira/browse/VALIDATOR-232
>             Project: Commons Validator
>          Issue Type: New Feature
>          Components: Framework
>            Reporter: Paul Benedict
>            Priority: Minor
>             Fix For: 1.4
>
>         Attachments: VALIDATOR-232.dtd.patch, VALIDATOR-232.patch
>
>
> Add a script="true|false" attribute to <field> to control whether JavaScript should be generated.
> Also see: https://issues.apache.org/struts/browse/STR-1888

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org