Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 95815 invoked from network); 3 Apr 2006 16:44:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Apr 2006 16:44:38 -0000 Received: (qmail 10831 invoked by uid 500); 3 Apr 2006 16:44:28 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 10766 invoked by uid 500); 3 Apr 2006 16:44:27 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 10750 invoked by uid 99); 3 Apr 2006 16:44:27 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Apr 2006 09:44:27 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [165.212.64.21] (HELO gateout01.mbox.net) (165.212.64.21) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Apr 2006 09:44:25 -0700 Received: from gateout01.mbox.net (gateout01.mbox.net [165.212.64.21]) by gateout01.mbox.net (Postfix) with ESMTP id 4990B2AA9 for ; Mon, 3 Apr 2006 16:44:03 +0000 (GMT) Received: from gateout01.mbox.net [127.0.0.1] by gateout01.mbox.net via mtad (C8.MAIN.3.27X) with ESMTP id 063kDcqSB0206Mo1; Mon, 03 Apr 2006 16:44:01 GMT Received: from gateout01.mbox.net [127.0.0.1] by gateout01.mbox.net via mtad (C8.MAIN.3.27X) with ESMTP id 057kDcqSa0020Mo1; Mon, 03 Apr 2006 16:43:59 GMT X-USANET-Routed: 2 gwsout-vs R:localhost:1825 Received: from GW2.EXCHPROD.USA.NET [165.212.116.254] by gateout01.mbox.net via smtad (C8.MAIN.3.27X); Mon, 03 Apr 2006 16:43:59 GMT X-USANET-Source: 165.212.116.254 IN mhn@recommind.com GW2.EXCHPROD.USA.NET X-USANET-MsgId: XID216kDcqSa6535Xo1 Received: from VS6.EXCHPROD.USA.NET ([10.116.208.162]) by GW2.EXCHPROD.USA.NET with Microsoft SMTPSVC(6.0.3790.211); Mon, 3 Apr 2006 10:43:59 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6573D.CE83A9B7" Subject: RE: ExceptionHandling with JSF and Tiles Date: Mon, 3 Apr 2006 10:43:55 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ExceptionHandling with JSF and Tiles Thread-Index: AcZTzU5YQaJkUpuuTq+OKEuhf80F3QDcBeOA From: "Michael Heinen" To: "MyFaces Discussion" X-OriginalArrivalTime: 03 Apr 2006 16:43:59.0720 (UTC) FILETIME=[CE960E80:01C6573D] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------_=_NextPart_001_01C6573D.CE83A9B7 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Has anybody a hint?=20 =20 ________________________________ From: Michael Heinen [mailto:mhn@recommind.com]=20 Sent: Donnerstag, 30. M=E4rz 2006 09:41 To: MyFaces Discussion Subject: ExceptionHandling with JSF and Tiles =20 Hi all, =20 I am still confused about Exception Handling. I know that this has been = discussed on many threads but I don't know how to handle exceptions=20 outside Actions/ActionListeners.=20 =20 My setup is MyFaces 1.1.1 and Tiles with the JspTilesViewHandlerImpl. =20 I can create FacesMessages and forward to any outcome page when an = exception occurs in an action/actionListener. This is working fine and = no problem. =20 I don't know how to handle serious errors in BackingBean constructors or = setters. I tried to catch them and re-throw them as FacesExceptions but my error = pages (defined in web.xml) are not displayed. =20 Instead of the error page the original requested tiles template is = partly processed. A ServletException is displayed in place of the tiles-part that caused = the error. e.g. ServletException in:/xxx.jsp] Cannot get value for expression = '#{ABackingBean.aValue}' =20 How do others handle exceptions with myFaces and Tiles? Are there any best practices? =20 Any help would be greatly appreciated. Michael ------_=_NextPart_001_01C6573D.CE83A9B7 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 
Has anybody a hint? =

 =

From: Michael Heinen [mailto:mhn@recommind.com]
Sent: Donnerstag, 30. = M=E4rz 2006 09:41
To: MyFaces Discussion
Subject: = ExceptionHandling with JSF and Tiles

 

Hi all,

 

I am still confused about Exception Handling. = I know that this has been discussed on many threads but I don't know how to = handle exceptions

outside Actions/ActionListeners. =

 

My setup is MyFaces 1.1.1 and Tiles with the JspTilesViewHandlerImpl.

 

I can create FacesMessages and forward to any = outcome page when an exception occurs in an action/actionListener. This is = working fine and no problem.

 

I don't know how to handle serious errors in BackingBean constructors or setters.

I tried to catch them and re-throw them as FacesExceptions but my error pages (defined in web.xml) are not displayed. 

Instead of the error page the original = requested tiles template is partly processed.

A ServletException is displayed in place of = the tiles-part that caused the error.

e.g. ServletException in:/xxx.jsp] Cannot get = value for expression '#{ABackingBean.aValue}'

  

How do others handle exceptions with myFaces = and Tiles?

Are there any best = practices?

 

Any help would be greatly = appreciated.

Michael

------_=_NextPart_001_01C6573D.CE83A9B7--