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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ISIS-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779855#comment-13779855 ] 

ASF subversion and git services commented on ISIS-547:
------------------------------------------------------

Commit e50e6d71d4a46abdaf56a80937980eb219458cc0 in branch refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=e50e6d7 ]

ISIS-547: better error logging

                
> Provide better error logging from the Wicket applicaiton init() method if Isis fails to boot.
> ---------------------------------------------------------------------------------------------
>
>                 Key: ISIS-547
>                 URL: https://issues.apache.org/jira/browse/ISIS-547
>             Project: Isis
>          Issue Type: Improvement
>          Components: Viewer: Wicket
>    Affects Versions: viewer-wicket-1.2.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: viewer-wicket-1.3.0
>
>
> 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).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira