[CAUSEWAY-547] Provide better error logging from the Wicket applicaiton init() method if Isis fails to boot.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: viewer-wicket-1.2.0
• Fix Version/s: viewer-wicket-1.3.0
• Component/s: Viewer Wicket
• Assignee: Daniel Keir Haywood
• Reporter: Daniel Keir Haywood
• Created: 27/Sep/13 12:03
• Updated: 25/Oct/13 09:34
• Resolved: 27/Sep/13 12:22

Description

This is a work-around for the fact that the Wicket framework's WicketFilter, that calls Application#init(), does not log any runtime exception that is thrown.

For example, if a missing JDBC driver has not been configured, then this fact is never logged explicitly.

The fix is to catch the runtime exception in the IsisWicketApplicaiton, and have it log before propogating the exception up to its caller (WicketFilter).

Issue Links

• relates to: WICKET-5376 Log the exception if the application cannot start properly