[
https://issues.apache.org/jira/browse/TAP5-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846627#action_12846627
]
Howard M. Lewis Ship commented on TAP5-1059:
--------------------------------------------
Convention over configuration: each library will automatically contribute a
"library.properties" from the root package of the library, perhaps?
> Mechanism for contributing to the application message catalog
> -------------------------------------------------------------
>
> Key: TAP5-1059
> URL: https://issues.apache.org/jira/browse/TAP5-1059
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
>
> There is now a way to inject the global message catalog into services.
> However, there is missing the ability to have libraries provide global
> messages.
> I propose a configuration point that is provided with an OrderedConfiguration
> of Resources; Tapestry will automatically contribute the Resource for the
> global message catalog (app.properties). Libraries will also contribute
> Resources if they have a global catalog; these will typically be contributed
> before the global message catalog so that the application message catalog can
> override keys from any library's message catalog (but the option exists to
> contribute after the global message catalog as well).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
