Return-Path: Delivered-To: apmail-portals-jetspeed-user-archive@www.apache.org Received: (qmail 11738 invoked from network); 9 Jan 2006 17:33:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Jan 2006 17:33:46 -0000 Received: (qmail 24615 invoked by uid 500); 9 Jan 2006 17:33:42 -0000 Delivered-To: apmail-portals-jetspeed-user-archive@portals.apache.org Received: (qmail 24583 invoked by uid 500); 9 Jan 2006 17:33:42 -0000 Mailing-List: contact jetspeed-user-help@portals.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jetspeed Users List" Delivered-To: mailing list jetspeed-user@portals.apache.org Received: (qmail 24553 invoked by uid 99); 9 Jan 2006 17:33:41 -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 09:33:41 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [216.23.125.30] (HELO mx.scriptall.com) (216.23.125.30) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jan 2006 09:33:41 -0800 Received: (qmail 28424 invoked by uid 512); 9 Jan 2006 12:33:26 -0500 Received: from david@bluesunrise.com by edison by uid 509 with qmail-scanner-1.22-st-qms (clamdscan: 0.75. spamassassin: 2.63. Clear:RC:1(64.105.95.102):. Processed in 0.028222 secs); 09 Jan 2006 17:33:26 -0000 X-Antivirus-MYDOMAIN-Mail-From: david@bluesunrise.com via edison X-Antivirus-MYDOMAIN: 1.22-st-qms (Clear:RC:1(64.105.95.102):. Processed in 0.028222 secs Process 28420) Received: from h-64-105-95-102.snvacaid.covad.net (HELO [192.168.1.143]) (david@bluesunrise.com@64.105.95.102) by mx.scriptall.com with SMTP; Mon, 09 Jan 2006 12:33:26 -0500 Message-ID: <43C29E5A.9050105@bluesunrise.com> Date: Mon, 09 Jan 2006 09:33:14 -0800 From: David Sean Taylor User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jetspeed Users List Subject: Re: How to handle exception ???? References: <1752C804BB00CF43AFBEA103357AD7AE059736E1@in-ex001.groupinfra.com> In-Reply-To: <1752C804BB00CF43AFBEA103357AD7AE059736E1@in-ex001.groupinfra.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Emandi, Srinivasrao wrote: > 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... > The portlet spec does not cover the declaration of error pages, but in your application you are free to forward to a JSP page on error. If you want the portal to handle the exception, throw a PortletException A new feature for configurable error pages handled by the portal would be valuable in my opinion --------------------------------------------------------------------- To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org For additional commands, e-mail: jetspeed-user-help@portals.apache.org