geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh Midha (JIRA)" <>
Subject [jira] Created: (GERONIMO-2621) Exception handling in Console
Date Mon, 04 Dec 2006 11:52:20 GMT
Exception handling in Console

                 Key: GERONIMO-2621
             Project: Geronimo
          Issue Type: Improvement
      Security Level: public (Regular issues)
          Components: console
    Affects Versions: 2.0
            Reporter: Rakesh Midha
         Assigned To: Rakesh Midha
             Fix For: 2.0

This improvement is discussed in

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 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.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message