click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian A. (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLK-660) ErrorPage should be an interface
Date Sun, 03 Nov 2013 10:09:17 GMT

    [ 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)

Mime
View raw message