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

          Joakim Olsson created issue -
          Howard M. Lewis Ship made changes -
          Field Original Value New Value
          Assignee Howard M. Lewis Ship [ hlship ]
          Howard M. Lewis Ship made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          Howard M. Lewis Ship made changes -
          Summary "Global" app.properties for a component-module Allow component libraries to contribute extra resources to the global application catalog
          Issue Type Wish [ 5 ] Improvement [ 4 ]
          Description When creating a component-module, there is currently no way to have a "global" app.properties as there is for a web-project. It would be nice to have this possibility to reduce duplication of label-translations etc. if a field is used in multiple components or pages for example.
          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).
          Howard M. Lewis Ship made changes -
          Status In Progress [ 3 ] Closed [ 6 ]
          Fix Version/s 5.2.0 [ 12314122 ]
          Resolution Fixed [ 1 ]
          Hide
          Massimo Lusetti added a comment -

          On Wed, May 12, 2010 at 12:51 AM, Howard M. Lewis Ship (JIRA)

          This is GREAT! ... Thanks!

          Cheers

          Massimo
          http://meridio.blogspot.com

          Show
          Massimo Lusetti added a comment - On Wed, May 12, 2010 at 12:51 AM, Howard M. Lewis Ship (JIRA) This is GREAT! ... Thanks! Cheers – Massimo http://meridio.blogspot.com
          Massimo Lusetti made changes -
          Link This issue is duplicated by TAP5-147 [ TAP5-147 ]

            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