You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2016/01/07 23:47:39 UTC

[jira] [Resolved] (VALIDATOR-280) create a fail-safe mode (maxlength)

     [ https://issues.apache.org/jira/browse/VALIDATOR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

No patch, seems unnecessary

> create a fail-safe mode (maxlength)
> -----------------------------------
>
>                 Key: VALIDATOR-280
>                 URL: https://issues.apache.org/jira/browse/VALIDATOR-280
>             Project: Commons Validator
>          Issue Type: New Feature
>         Environment: any
>            Reporter: Ralf Hauser
>
> with the fail-safe-mode enabled, every input has a maxlength validation with at most 100 characters.
> So, if a developer forgets to specify a rule, this would apply in any case.
> This is kind of a shift from an opt-in paradigm to an opt-out paradigm.
> If for a specific field the max length is different from 100, then it is the task of the developer to specify this in validation.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)