[CAUSEWAY-625] Better reporting of metamodel violation errors

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: viewer-wicket-1.3.1, core-1.3.0
• Fix Version/s: viewer-wicket-1.4.0, core-1.4.0
• Component/s: Core, Viewer Wicket
• Assignee: Daniel Keir Haywood
• Reporter: Daniel Keir Haywood
• Created: 06/Dec/13 14:55
• Updated: 11/Mar/14 07:39
• Resolved: 06/Dec/13 16:22

Description

Currently metamodel exceptions are rather difficult to spot in the exception log, and there is no indication of an exception in the running applicaiotn - just a nasty stacktrace.

Both of these should be addressed... attempting to access the webapp should show the metamodel exceptions that occurred.