[TAP5-2341] Can't specify a regexp validator with a comma

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Won't Fix
• Affects Version/s: 5.3.7
• Component/s: tapestry-core
• Assignee: Unassigned
• Reporter: Tony Nelson
• Created: 27/May/14 20:45
• Updated: 27/May/14 22:06
• Resolved: 27/May/14 22:03

Description

Trying to validate a two decimal numeric input with"

            <t:textfield t:id="erpfte" class="input-mini" value="quota.erp"
                         translate="prop:twoDecimal" validate="regexp=^\d+(?:\.\d{1,2})?$" />

Generates this partial stack trace:

Caused by: java.lang.RuntimeException: Unexpected character '2' at position 22 of input string: regexp=^\d+(?:\.\d{1,2})?$
	at org.apache.tapestry5.internal.services.FieldValidatorSourceImpl.parseError(FieldValidatorSourceImpl.java:423)
	at org.apache.tapestry5.internal.services.FieldValidatorSourceImpl.parse(FieldValidatorSourceImpl.java:315)
	at org.apache.tapestry5.internal.services.FieldValidatorSourceImpl.toValidatorSpecifications(FieldValidatorSourceImpl.java:200)
	at org.apache.tapestry5.internal.services.FieldValidatorSourceImpl.createValidators(FieldValidatorSourceImpl.java:183)

Looking through the code, it appears the parser thinks the comma ends the current validator and is starting another.

Issue Links

• duplicates: TAP5-520 Using regular expressions with the @Validate annotation causes odd parse errors if the regexp includes common characters (including commas)