[
https://issues.apache.org/jira/browse/TAP5-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643519#action_12643519
]
Thiago H. de Paula Figueiredo commented on TAP5-253:
----------------------------------------------------
The ValidationMessagesSource contribution does not work even when you add a
properties file for a locale that Tapestry does not have default messages yet.
I've added this method to my AppModule.
public static void contributeValidationMessagesSource(Configuration<String>
configuration) {
configuration.add("classpath:/ValidationMessages");
}
After a lot of digging and debugging in the tapestry-core sources, I've found
that in the
ValidationMessagesSourceImpl.ValidationMessagesSourceImpl(Collection<String>
bundles, Resource classpathRoot, URLChangeTracker tracker), that my
ValidationMessages.properties is used as the parent bundle to the default
Tapestry validation properties file. It should be exactly the other way. My
validation messages do not override the defaults.
Shouldn't the ValidationMessagesSource service receive an OrderedConfiguration
intead of a Configuration? The ordering of the contributions seems to be an
issue here.
> Default validation messages only overridable individually
> ---------------------------------------------------------
>
> Key: TAP5-253
> URL: https://issues.apache.org/jira/browse/TAP5-253
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.15
> Reporter: Andy Blower
> Priority: Minor
>
> I'm trying to set up validation for our forms and I need to customise the
> default validation messages. Unfortunately there doesn't seem to be a way to
> do this as contributing to ValidationMessagesSource just adds new messages
> for new validators. I need to change the default messages to what we need.
> I know that we can override the message for each field name in the message
> catalogs, but this is undesirable (& expensive with extra translations
> needed) because they'll all be the same. The only solution I've found is to
> override this with a properties file in the tapestry5.internal package but
> this doesn't work in every environment so it's not really a good solution.
--
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]
