Return-Path: 
 <jetspeed-user-return-20148-apmail-portals-jetspeed-user-archive=portals.apache.org@portals.apache.org>
Delivered-To: apmail-portals-jetspeed-user-archive@www.apache.org
Received: (qmail 44674 invoked from network); 9 Jan 2006 13:17:28 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 9 Jan 2006 13:17:28 -0000
Received: (qmail 70901 invoked by uid 500); 9 Jan 2006 13:17:19 -0000
Delivered-To: apmail-portals-jetspeed-user-archive@portals.apache.org
Received: (qmail 70866 invoked by uid 500); 9 Jan 2006 13:17:18 -0000
Mailing-List: contact jetspeed-user-help@portals.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:jetspeed-user-help@portals.apache.org>
List-Unsubscribe: <mailto:jetspeed-user-unsubscribe@portals.apache.org>
List-Post: <mailto:jetspeed-user@portals.apache.org>
List-Id: <jetspeed-user.portals.apache.org>
Reply-To: "Jetspeed Users List" <jetspeed-user@portals.apache.org>
Delivered-To: mailing list jetspeed-user@portals.apache.org
Received: (qmail 70854 invoked by uid 500); 9 Jan 2006 13:17:18 -0000
Delivered-To: apmail-jakarta-jetspeed-user@jakarta.apache.org
Received: (qmail 70850 invoked by uid 99); 9 Jan 2006 13:17:18 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jan 2006 05:17:18 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of jak-jetspeed-user@m.gmane.org
 designates 80.91.229.2 as permitted sender)
Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jan 2006 05:17:17 -0800
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1Evwt6-0006zP-3e
	for jetspeed-user@jakarta.apache.org; Mon, 09 Jan 2006 14:16:43 +0100
Received: from CPE000f6636b02a-CM014480016982.cpe.net.cable.rogers.com
 ([72.139.90.69])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <jetspeed-user@jakarta.apache.org>;
 Mon, 09 Jan 2006 14:16:40 +0100
Received: from aaronmevans by
 CPE000f6636b02a-CM014480016982.cpe.net.cable.rogers.com with local (Gmexim
 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <jetspeed-user@jakarta.apache.org>;
 Mon, 09 Jan 2006 14:16:40 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: jetspeed-user@jakarta.apache.org
From: Aaron Evans <aaronmevans@yahoo.ca>
Subject: Re: How to handle exception ????
Date: Mon, 9 Jan 2006 13:16:34 +0000 (UTC)
Lines: 33
Message-ID: <loom.20060109T140823-861@post.gmane.org>
References: <1752C804BB00CF43AFBEA103357AD7AE059736E1@in-ex001.groupinfra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: main.gmane.org
User-Agent: Loom/3.14 (http://gmane.org/)
X-Loom-IP: 72.139.90.69 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.12) Gecko/20050915 Firefox/1.0.7)
Sender: news <news@sea.gmane.org>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Emandi, Srinivasrao <srinivas.emandi <at> logicacmg.com> writes:

> 
> Hi all
> 	Can any one say , how to handle exception in portlet. Is there is any concept
of configuring an error page in
> portlet.xml as if it was done in web.xml.
> 	If any runtime excetion occurs i want to forward to error page, how to handle
this...
> Thanks in advance...

I do not believe that there is any error page configuration for portlet in the 
portlet.xml like there is for servlets in web.xml.

Remember that you don't have control over certain aspects of the http response 
as this is the reponsibility of the portlet container/portal itself as it 
presents an aggregated view of many portlets.  So it would not make sense to 
base it on http error codes like in the servlet web.xml because the portal
is going to return 200, even if your portlet has an error.

I guess the question becomes, does J2 have any features for configuring
some kind of error display for exceptions generated by individual portlets.

In any event, if you are developing your own portlets, my suggestion would be
this:

In your doView, doEdit, doHelp methods, wrap everything in a try/catch block,
and then in the catch, do an include of an error JSP page in your application.







---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org