Tapestry 5
  1. Tapestry 5
  2. TAP5-424

Allow component libraries to contribute extra resources to the global application catalog

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.0, 5.1, 5.0.18, 5.0.19
    • Fix Version/s: 5.2.0
    • Component/s: None
    • Labels:
      None

      Description

      Components in libraries have the same desire to share common message strings that components in an application do.

      My earlier thoughts were to define a way to have a lib.properties for a component library.

      However, my current thinking is to extend ComponentMessagesSource (the source for the application message catalog as well) so that component libraries can contribute Resources for message catalogs into the global message catalog (typically, before the app.properties file, so that an application has the ability to override specific component library messages).

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Howard M. Lewis Ship
              Reporter:
              Joakim Olsson
            • Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development