[
http://jira.jboss.com/jira/browse/JBPORTAL-1466?page=comments#action_1236... ]
Varsha Paranjape commented on JBPORTAL-1466:
--------------------------------------------
The usecase that we currently have is -
The WAP Customer is creating a Customer Portal Application, this is a web application
built on the Portal that is composed out of Themes, Layouts, Portal Metadata, a collection
of Product Portlets, and a set of instances of WAP Customizable Portlets that represent
features that are general and reusable across product offerings.
The WAP Customer creates instances of WAP Customizable Portlets in their Customer Portal
Application.
The WAP Customizable Portlet is a JSF Bridge based Portlet because we will also offer
stand alone non-portal implementations of this customizable component.
The WAP Customer wants to customize the styles and branding to match that of their
Customer Portal Application.
The WAP Customer would like to be able to customize the error display that occurs for an
unhandled exception in the WAP Customizable Portlet.
Our proposal is that there be an option to allow them to include in their Portal
application a web.xml <error-page> declaration for a .jsp that will be used in place
of the current portlet view in the case of an error.
This makes it easy for us to support both the portlet and non-portlet versions of this
customization, eases porting, and doesn't create new and unfamiliar configuration for
users.
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