You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Vladimir Velikiy (JIRA)" <ji...@apache.org> on 2010/10/20 14:58:22 UTC

[jira] Created: (TAP5-1318) Client Pattern constraint validator does not work correctly

Client Pattern constraint validator does not work correctly
-----------------------------------------------------------

                 Key: TAP5-1318
                 URL: https://issues.apache.org/jira/browse/TAP5-1318
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-beanvalidator
    Affects Versions: 5.2.1
            Reporter: Vladimir Velikiy
            Priority: Critical


Error object field name for parameter spec in tapestry-beanvalidator.js (spec.pattern in place of spec.regexp):

currently in 5.2.1 version:

Tapestry.Validator.pattern = function(field, message, spec)
{
	Tapestry.Validator.regexp(field, message, spec.pattern);
};

must be:

Tapestry.Validator.pattern = function(field, message, spec)
{
	Tapestry.Validator.regexp(field, message, spec.regexp);
};

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


[jira] Closed: (TAP5-1318) Client Pattern constraint validator does not work correctly

Posted by "Andreas Andreou (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Andreou closed TAP5-1318.
---------------------------------

    Resolution: Duplicate

> Client Pattern constraint validator does not work correctly
> -----------------------------------------------------------
>
>                 Key: TAP5-1318
>                 URL: https://issues.apache.org/jira/browse/TAP5-1318
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-beanvalidator
>    Affects Versions: 5.2.1
>            Reporter: Vladimir Velikiy
>            Priority: Critical
>
> Error object field name for parameter spec in tapestry-beanvalidator.js (spec.pattern in place of spec.regexp):
> currently in 5.2.1 version:
> Tapestry.Validator.pattern = function(field, message, spec)
> {
> 	Tapestry.Validator.regexp(field, message, spec.pattern);
> };
> must be:
> Tapestry.Validator.pattern = function(field, message, spec)
> {
> 	Tapestry.Validator.regexp(field, message, spec.regexp);
> };

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


[jira] Closed: (TAP5-1318) Client Pattern constraint validator does not work correctly

Posted by "Andreas Andreou (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Andreou closed TAP5-1318.
---------------------------------

    Resolution: Duplicate

> Client Pattern constraint validator does not work correctly
> -----------------------------------------------------------
>
>                 Key: TAP5-1318
>                 URL: https://issues.apache.org/jira/browse/TAP5-1318
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-beanvalidator
>    Affects Versions: 5.2.1
>            Reporter: Vladimir Velikiy
>            Priority: Critical
>
> Error object field name for parameter spec in tapestry-beanvalidator.js (spec.pattern in place of spec.regexp):
> currently in 5.2.1 version:
> Tapestry.Validator.pattern = function(field, message, spec)
> {
> 	Tapestry.Validator.regexp(field, message, spec.pattern);
> };
> must be:
> Tapestry.Validator.pattern = function(field, message, spec)
> {
> 	Tapestry.Validator.regexp(field, message, spec.regexp);
> };

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