Tapestry
  1. Tapestry
  2. TAPESTRY-1760

Contrib:Table column ids mangled: underscores become periods so column heading lookup fails

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 4.1.3
    • Fix Version/s: 4.1.5
    • Component/s: Contrib
    • Labels:
      None

      Description

      Until 4.1.3, this was valid:

      <table jwcid="table@contrib:Table" columns="User_firstName_colhdg:firstName, User_lastName_colhdg:lastName" ...

      The Table component would produce column headings by using "User_firstName_colhdg" and "User_lastName_colhdg" as message keys.

      But now, the underscores are replaced by periods (ie. dots) on the fly and the lookup fails, so it outputs these unhappy column headings:

      User.firstName.colhdg User.lastName.colhdg

      The doco states "the title of the column will be taken from translation strings of the component by using the column id as a key" at http://tapestry.apache.org/tapestry4.1/tapestry-contrib/componentreference/table.html.

      A workaround for anyone experiencing this problem is to change all underscores in the affected message keys from underscores to dots - this means throughout your code and in the message properties files. This may of course be quite error-prone in large systems.

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Jesse Kuhnert
              Reporter:
              Geoff Callender
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development