Benjamin Weidig commented on TAP5-2550:

Sounds reasonable.

I no longer have a Tapestry5 source dev setup and much free time currently, so 
it might take a little to prepare a new patch.

> 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: Wish
>    Affects Versions: 5.4.1
>            Reporter: I D
>            Priority: Major
>         Attachments: 0001-TAP5-2550-Added-new-missing-messages-handling.patch
> Currently, whenever a message catalog lookup fails, tapestry returns the 
> placeholder String {{[[missing key: key-not-found]]}}. This behavior is 
> implemented in {{AbstractMessages.get()}}.
> 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

Reply via email to