[jira] [Resolved] (TAP5-147) Localization: Messages should be overwiteable by Container (.i.e. users) of the component

["Massimo Lusetti (JIRA)" <ji...@apache.org>]

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

Massimo Lusetti resolved TAP5-147.
----------------------------------

    Resolution: Duplicate

Is has been fixed with TAP5-424 as now the ComponentMessagesSource accept and ordered configuration of catalogs (Resources) so order determine overrides.

> Localization: Messages should be overwiteable by Container (.i.e. users) of the component 
> ------------------------------------------------------------------------------------------
>
>                 Key: TAP5-147
>                 URL: https://issues.apache.org/jira/browse/TAP5-147
>             Project: Tapestry 5
>          Issue Type: New Feature
>    Affects Versions: 5.0.15
>            Reporter: Fritz Pröbstle
>            Assignee: Massimo Lusetti
>              Labels: tapestry5-review-for-closing
>
> Currently messages are *only* searched in the component and its subclasses catalogs.
> This means only the component provider suppies messages.
> Often a *User* of a componet ( ie. the container ) wants to override the messages.
> In a special case the container is the page which should have means to change *all* messages.
> I propose a path-like syntax to specify thew hierarchy.(means all messages are reachable if the container hierarchy is documented)
> I.e:
> page.properties
> -------------------
> firstContainerId.innerContainerId.name= overwriten message
> In the Message search  for a component it the following search would appear:
>    look in immediate container
>    ...
>    look in the moust outer container (page)
>    the look upo in the componet and its subclasses.
> If a message is found stop the search and take the message.
>   

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira