[ 
https://issues.apache.org/jira/browse/TAP5-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Howard M. Lewis Ship updated TAP5-253:
--------------------------------------

    Description: 
I'm trying to set up validation for our forms and I need to customize 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.


  was:
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.


        Summary: Unable to effectively override default validation messages 
globally  (was: Default validation messages only overridable individually)

My original thought with ValidationMessagesSource was that a new 3rd party 
validator or translator that wanted to provide its own set of default 
validation messages would contribute its own bundle.  Order wasn't important 
(thus Collection, not List) since there would not be any naming conflicts; it 
would be entirely new keys.

However, I now understand the desire to override built-in messages using a 
secondary bundle.

I think this can be taken care of, it will affect the contributions, since it 
will now be an OrderedConfiguration.

> Unable to effectively override default validation messages globally
> -------------------------------------------------------------------
>
>                 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
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>
> I'm trying to set up validation for our forms and I need to customize 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]

Reply via email to