Mailing-List: contact dev-help@click.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@click.apache.org
Date: Sun, 3 Nov 2013 10:09:17 +0000 (UTC)
From: "Adrian A. (JIRA)" <jira@apache.org>
To: dev@click.apache.org
Message-ID: <JIRA.12462298.1271469271830.12514.1383473357128@arcas>
In-Reply-To: <JIRA.12462298.1271469271830@arcas>
References: <JIRA.12462298.1271469271830@arcas>
Subject: [jira] [Commented] (CLK-660) ErrorPage should be an interface
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Adrian A. commented on CLK-660:
-------------------------------

> I propose we add an ErrorHandler interface which any Page, that subclasses BorderPage, can implement.

How to handle situations where the error happens in the BorderPage too (or other parent of BorderPage if present)?

Being standalone (and very well tested) ensures that if error happen *everywhere*, it can always show up.

> ErrorPage should be an interface
> --------------------------------
>
>                 Key: CLK-660
>                 URL: https://issues.apache.org/jira/browse/CLK-660
>             Project: Click
>          Issue Type: Improvement
>          Components: core
>            Reporter: Bob Schellink
>             Fix For: 3.0.0
>
>
> As ErrorPage extends Page, it won't inherit the features and look and feel from the application BorderPage.
> I propose we add an ErrorHandler interface which any Page, that subclasses BorderPage, can implement.


--
This message was sent by Atlassian JIRA
(v6.1#6144)