geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevan Miller (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-2621) Exception handling in Console
Date Fri, 01 Feb 2008 07:07:08 GMT

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

Kevan Miller closed GERONIMO-2621.
----------------------------------

    Resolution: Won't Fix

The console has been extensively reworked. If we want to take up this effort, again, please
reopen or create a new jira.

> Exception handling in Console
> -----------------------------
>
>                 Key: GERONIMO-2621
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2621
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: console
>    Affects Versions: 2.0-M5
>            Reporter: Rakesh Midha
>            Assignee: Rakesh Midha
>             Fix For: 2.1
>
>         Attachments: deployExp.patch
>
>
> This improvement is discussed in http://comments.gmane.org/gmane.comp.java.geronimo.devel/41449
> In case I get any exception or error condition in Console, the nothing is printed on
web console and huge stack trace is printed on server console. Only thing done in the name
of Exception handling in all the portlets is "throw PortletException"
> I somehow don't like this behavior of console. As a console user I don't want to go and
see server stacktrace, if there is some error I should atleast be informed in console. I think
everytime there is a error or exception in console, it should be printed in either exception
page in webconsole, or in header of portlet view page. This is done to some extent in configManager
and CA part of console. But not in uniform way.
> This is what I am proposing for Exception handling in console :
> 1. Create a ConsoleException.java which extends PortletException, this class will have
overridden printStackTrace(PrintWriter), which will set attribute required in _ConsoleException.jsp
apart from printing the stack on PrintWriter.
> 2. Create _ConsoleException.jsp which should be included in all portlet, this jsp will
be responsible to print a short message and long stack trace. (with a toggle button to view
and hide long stack trace)
> 3. All Portlet classes should throw ConsoleException instead of PortletException
> I think this will be nice and cleaner way to handle the console problems. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message