On Fri, Dec 4, 2009 at 7:37 AM, Igor Drobiazko <igor.drobia...@gmail.com> wrote:
> This would be a nice addition but does not solve the problem. Components are > reusable and their message catalog should be reusable too. I don't want to > provide messages for a component in every page using it. What is needed is > just a "redirect" to another package to look for message catalog. As you said it would be an addition so an extension like system... > Now the messages are searched in a low-specific to a most-specific order. If > a component message catalog contains an entry for a particular key the > application wide catalog will be never considered. So you don't have any > chance to override existing translations of a component. For backward > compatibility reasons this behavior should not be changed. Well even i perfectly understand the "backward compatibilty" shield effect i think that some thoughts should be deserved to such an option. Cheers -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
