[CAUSEWAY-599] Better message and diagnostics for Exception Recognizers

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: archetype-simple-wrj-1.3.1, archetype-quickstart-wrj-1.3.1, objectstore-jdo-1.3.0, core-1.3.0
• Fix Version/s: archetype-simple-wrj-1.4.0, archetype-quickstart-wrj-1.4.0, objectstore-jdo-1.4.0, core-1.4.0
• Component/s: Core, Persistence JDO, ZZZ Archetype: SimpleApp
• Assignee: Daniel Keir Haywood
• Reporter: Daniel Keir Haywood
• Created: 21/Nov/13 13:26
• Updated: 20/Feb/15 14:07
• Resolved: 21/Nov/13 17:28

Description

When a registered ExceptionRecognizer recognizes an exception, it parses the exception message and returns a user-friendly message to display. Nothing is logged.

Currently the parsed message returned is parsed from the outer-most exception; for better information it should instead parse the root cause.

For the developer, it would be useful for the exceptions to be logged. One way to do this might be to make them logged if running in prototype mode, but not logged otherwise.