You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org> on 2007/03/04 20:06:50 UTC
[jira] Updated: (TAPESTRY-698) Validation messages are too hard
wired to the built-in set of translators and validators
[ https://issues.apache.org/jira/browse/TAPESTRY-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-698:
-----------------------------------
Fix Version/s: (was: 4.1.2)
4.2
> Validation messages are too hard wired to the built-in set of translators and validators
> ----------------------------------------------------------------------------------------
>
> Key: TAPESTRY-698
> URL: https://issues.apache.org/jira/browse/TAPESTRY-698
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Fix For: 4.2
>
>
> Because validation messages are defined in terms of a properties file, there isn't an avenue for introducing new, localized, messages (that can then be overridden).
> Ideally, there should be a configuration point that allows new messages to be defined; the ValidationMessages interface should be aware of these messages and search them. Assuming the configuration was searched before ValidStrings.properties, this would also provide an easy way to override a default validation message throughout the application.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org