You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "I D (JIRA)" <ji...@apache.org> on 2016/05/22 15:00:15 UTC
[jira] [Updated] (TAP5-2550) Optionally throw an exception on
message catalog lookup failures
[ https://issues.apache.org/jira/browse/TAP5-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
I D updated TAP5-2550:
----------------------
Description:
Currently, whenever a message catalog lookup fails, tapestry returns the placeholder String {code}[[missing key: key-not-found]]{code}. This behavior is implemented in {code}AbstractMessages.get(){code}.
In a way, this is a silent failure, and the one who sees this string is more likely the app's end user than the tapestry user.
It would be great if there would be a global configuration property (e.g. SymbolConstants.EXCEPTION_ON_MISSING_MESSAGE, defaulting to false) allowing us to instruct tapestry to throw an exception instead (perhaps a NoSuchElementException).
was:
Currently, whenever a message catalog lookup fails, tapestry returns the placeholder String {code}[[missing key: key-not-found]]{code}. This behavior is implemented in {code}AbstractMessages.get(){code}.
In a way, this is a silent failure, and the one who sees this string is more likely the app's end user than the tapestry user.
It would be great if there would be a global configuration property (e.g. SymbolConstants.EXCEPTION_ON_MISSING_MESSAGE, defaulting to false) allowing us to instruct tapestry to throw an exception instead.
> Optionally throw an exception on message catalog lookup failures
> ----------------------------------------------------------------
>
> Key: TAP5-2550
> URL: https://issues.apache.org/jira/browse/TAP5-2550
> Project: Tapestry 5
> Issue Type: Bug
> Affects Versions: 5.4.1
> Reporter: I D
>
> Currently, whenever a message catalog lookup fails, tapestry returns the placeholder String {code}[[missing key: key-not-found]]{code}. This behavior is implemented in {code}AbstractMessages.get(){code}.
> In a way, this is a silent failure, and the one who sees this string is more likely the app's end user than the tapestry user.
> It would be great if there would be a global configuration property (e.g. SymbolConstants.EXCEPTION_ON_MISSING_MESSAGE, defaulting to false) allowing us to instruct tapestry to throw an exception instead (perhaps a NoSuchElementException).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)