tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "I D (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TAP5-2550) Optionally throw an exception on message catalog lookup failures
Date Sun, 22 May 2016 14:53:13 GMT
I D created TAP5-2550:
-------------------------

             Summary: 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message