Ditto and I would add start with very specific exceptions (IOException) and fall to more general exceptions later on (Exception)
If you want to redirect output to an awaiting Log Server or reformat to HTML take a look at Log4j
HTH,


Martin Gainty
(mobile) 617-852-7822


From: "Leon Rosenberg" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
To: "'Struts Users Mailing List'" <user@struts.apache.org>
Subject: AW: Tiles is hiding my jsp error messages?!
Date: Tue, 1 Feb 2005 15:00:54 +0100
MIME-Version: 1.0
Received: from mail.apache.org ([209.237.227.199]) by mc7-f28.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 1 Feb 2005 06:02:38 -0800
Received: (qmail 30437 invoked by uid 500); 1 Feb 2005 14:02:14 -0000
Received: (qmail 30397 invoked by uid 99); 1 Feb 2005 14:02:13 -0000
Received: pass (hermes.apache.org: local policy)
Received: from h-213.61.151.32.host.de.colt.net (HELO anotheria.net) (213.61.151.32) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 01 Feb 2005 06:02:11 -0800
Received: from dragonfire ([84.128.66.213]) by anotheria.net for <[EMAIL PROTECTED]> with eXtremail; Tue, 1 Feb 2005 16:56:46 +0100
X-Message-Info: JGTYoYF78jGI5G3rXjm4M/TmGZNnDiYgtmAbYB3woW0=
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <mailto:[EMAIL PROTECTED]>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Post: <mailto:user@struts.apache.org>
List-Id: "Struts Users Mailing List" <user.struts.apache.org>
Delivered-To: mailing list user@struts.apache.org
X-ASF-Spam-Status: No, hits=0.9 required=10.0tests=FORGED_RCVD_HELO,PLING_QUERY
X-Spam-Check-By: apache.org
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
thread-index: AcUIdbiHfGjUeZWbS+CJWJnetB7ZogAD3fmA
X-Virus-Checked: Checked
Return-Path: [EMAIL PROTECTED]
X-OriginalArrivalTime: 01 Feb 2005 14:02:39.0061 (UTC) FILETIME=[B07D3850:01C50866]


> Or, if that doesn't help, step 2 (for me) is to remove the
> entire contents of that particular tile, and slowly replace
> it piece by piece until it stops rendering, then examine the
> part you just put back.  I know that sounds crazy, but it
> works for me.....and it almost always ends with "(head
> smack)...what was I thinking?".

The far more easier debug opportunity is to insert try/catch blocks in each
included page.
And print the exception to stdout/log :-)
:-)





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to