You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2013/10/25 11:34:36 UTC

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

     [ https://issues.apache.org/jira/browse/ISIS-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood closed ISIS-547.
----------------------------


> 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 was sent by Atlassian JIRA
(v6.1#6144)