[jira] [Updated] (TAP5-721) missing message key fail with exception

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-721:
--------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> missing message key fail with exception
> ---------------------------------------
>
>                 Key: TAP5-721
>                 URL: https://issues.apache.org/jira/browse/TAP5-721
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.2
>            Reporter: Joost Schouten
>              Labels: bulk-close-candidate
>
> I would like a way to tell tapestry to thrown an exception on encountering a missing message key. Printing of the "missing key" message on the page results in silent failure especially for larger apps.
> I would propose adding a boolean symbol along the lines of MISSING_MESSAGE_KEY_FAIL_WITH_EXCEPTION which defaults to false.



--
This message was sent by Atlassian JIRA
(v6.2#6252)