[
https://issues.apache.org/jira/browse/TAP5-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-147.
-------------------------------------
Resolution: Won't Fix
This is a significant change in behavior that I suspect would cause as many
problems as it solves. Have messages passed into components as parameters, with
defaults coming from the component's message catalog.
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
