Tapestry
  1. Tapestry
  2. TAPESTRY-1765

getting language independent messages fails

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 4.1.3
    • Fix Version/s: 4.1.7
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      WinXP SP2, Java 1.5.0_11, Tapestry 4.1.3, Hivemind 1.1.1

      Description

      When I call getMessages().getMessage() in a page with a message key, which only exists in the default properties file (app.properties, and not in app_de.properties for example), no message is being returned, but only the key "[MESSAGE_KEY]". Before the update from Tapestry 4.1.2 to 4.1.3, this problem did not occured.

        Issue Links

          Activity

            People

            • Assignee:
              Ulrich Stärk
              Reporter:
              Christian Nutz
            • Votes:
              7 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Development