[
https://issues.apache.org/jira/browse/TAPESTRY-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508158
]
Kevin J. Menard, Jr. commented on TAPESTRY-572:
-----------------------------------------------
Like I said, I'll go with Paul's approach. It seems to make sense that the
validators should handle non-native datatype validation. But, if your
assessment of the translator system is correct, then it's really only
applicable for read-only values, unless of the proper type, since the
translation is only done in one direction. So, if it were intended to be a
data marshalling service, its utility is limited.
> 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]
