You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/01/12 09:10:55 UTC
[jira] [Closed] (TAP5-721) missing message key fail with exception
[ https://issues.apache.org/jira/browse/TAP5-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade closed TAP5-721.
-------------------------------
Resolution: Invalid
We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.
> 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.3.4#6332)