[jira] [Commented] (TAP5-2550) Optionally throw an exception on message catalog lookup failures

2018-02-04 Thread Benjamin Weidig (JIRA)
[ https://issues.apache.org/jira/browse/TAP5-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16352082#comment-16352082 ] Benjamin Weidig commented on TAP5-2550: --- Sounds reasonable. I no longer have a Tapestry5 source dev

[jira] [Commented] (TAP5-2550) Optionally throw an exception on message catalog lookup failures

2018-02-04 Thread Bob Harner (JIRA)
[ https://issues.apache.org/jira/browse/TAP5-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16351894#comment-16351894 ] Bob Harner commented on TAP5-2550: -- To simplify things a bit, I think there should only be two behaviors:

[jira] [Commented] (TAP5-2550) Optionally throw an exception on message catalog lookup failures

2017-01-01 Thread Benjamin Weidig (JIRA)
[ https://issues.apache.org/jira/browse/TAP5-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15791142#comment-15791142 ] Benjamin Weidig commented on TAP5-2550: --- Because I'm sometimes fail to see missing message keys I