[jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1466) customizable error page in the portlet that threw the exception

[Julien Viet (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1466?page=comments#action_12364299 ] 
            
Julien Viet commented on JBPORTAL-1466:
---------------------------------------

you mean as a portal object property that would be inherited in the hierarchy ? like root -> portal -> page -> page

I am working on abstracting the error handling in one class, the class implementation would look up the SHOW/HIDE properties in the portal object and in addition to that would contain a reference to an URI for doing a request dispatch to an error page like :

"/WEB-INF/jsp/header/tabs.jsp" where the resource tabs.jsp would be in portal-core.war

it would be accessed by a request dispatch and we could set request attributes properties with the error nature and such.


> customizable error page in the portlet that threw the exception
> ---------------------------------------------------------------
>
>                 Key: JBPORTAL-1466
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1466
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.CR2
>            Reporter: William DeCoste
>         Assigned To: Julien Viet
>
> Feature request from customer.
> Feature:
> For error handing, the portlet should be able to render a customizable error page in the portlet that threw the exception. This feature would be something similar to the error-page tag in web.xml.
> Currently JBoss Portal provides a way to either hide the portlet that has errors or show it with the stack trace or show it with only the error message. But there is no way where the developers could customize the contents that appear in the window for the portlet that throws an exception.
>  We had opened case #00015844 about not being able to use web.xml error-page tag with JBoss portal applications. The provided solution about catching the specific exception in the render method does not work as it is not customizable & too tied up with the portlet class code. And as you might be aware about the WAP function - someone using the WAP application components will not be able to customize it according to their requirements.
>  
> We know that the portlet standard doesn't specify what to do, and we're just trying to have it behave as much like a regular web application in lieu of something being in the standard.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira