[
https://issues.apache.org/jira/browse/TAPESTRY-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508022
]
Kevin J. Menard, Jr. commented on TAPESTRY-572:
-----------------------------------------------
I think I actually meant NumberTranslator. I had to dig into my code to
verify, but I don't use the T3 validation system at all. Indeed, it looks like
the problem is still around with a number translator (<binding
name="translator" value="translator:number"/>).
Should I open a new issue or edit this one?
> NumberValidator should accept Strings
> -------------------------------------
>
> Key: TAPESTRY-572
> URL: https://issues.apache.org/jira/browse/TAPESTRY-572
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.0
> Reporter: Kevin J. Menard, Jr.
> Priority: Minor
> Fix For: 4.1.2
>
>
> Applying NumberValidator to a TextField will allow a number to be validated
> as a number and stored as a String. However, NumberValidator is not able to
> take a String and display it as a number. I think this should be a
> bidirectional process. An example of where this would be useful is the
> following:
> I'd like to store a number as a String so I don't lose any prepending 0's
> (which RDBMSs love to throw out) when persisting the data. However, I do
> want to ensure that only a number is valid input.
--
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]
