tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fritz Pröbstle (JIRA) <j...@apache.org>
Subject [jira] Reopened: (TAP5-147) Localization: Messages should be overwiteable by Container (.i.e. users) of the component
Date Tue, 26 May 2009 10:31:45 GMT

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

Fritz Pröbstle reopened TAP5-147:

1:) Sorry this feature is vital for reusing components.
Specialy tapestry which is compoent centric should implement this aspect.
 isn't is a general rule , thst the User of a compoents could configure it properties?

2:) if it will not be implemented, is there a  workaround ??

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

View raw message