You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Ulrich Stärk (JIRA)" <ji...@apache.org> on 2009/02/17 11:07:59 UTC

[jira] Commented: (TAP5-520) Regexp validator parse error

    [ https://issues.apache.org/jira/browse/TAP5-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674162#action_12674162 ] 

Ulrich Stärk commented on TAP5-520:
-----------------------------------

I bet this is because tapestry thinks that after the comma, a new validator will follow. Can't you rewrite your regexp to not contain the {2,4} constraint? Is that necessary at all with the + quantifier in place?

> Regexp validator parse error
> ----------------------------
>
>                 Key: TAP5-520
>                 URL: https://issues.apache.org/jira/browse/TAP5-520
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.18
>            Reporter: Konstantin Miklevskiy
>
> Try adding this field to your form:
> @Validate("regexp=^([a-zA-Z0-9]{2,4})+$")
> private String somefield;
> Page will fail to render with exception saying:
> Render queue error in BeginRender[mypage.somefield]: Failure reading parameter 'validate' of component mypage.somefield: Coercion of ^([a-zA-Z0-9]{2 to type java.util.regex.Pattern (via String --> java.util.regex.Pattern) failed: Unclosed counted closure near index 15 ^([a-zA-Z0-9]{2 ^

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