[
https://issues.apache.org/jira/browse/VALIDATOR-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511424
]
Paul Benedict commented on VALIDATOR-232:
-----------------------------------------
Niall, I agree with the example you provided. I think it is a valuable
enhancement to allow people to determine which fields can fail-fast at the
client, but others for back-end processing. Because I don't have this ability,
neither do I use javascript at all on my Struts apps.
I prefer the scriptable attribute over custom validator because it is not
use-case specific. A company may have different requirements, for example, for
an intranet than an internet. Or if there is a bug in a javascript validator,
instead of waiting for the next release, a company could switch it off just for
the problematic fields.
So I see a lot of value in this feature.
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
