PROTECTED]
Sent: Wednesday, November 28, 2001 1:40 PM
Subject: Struts Error Page Approach - Recommended /
Struts Support
Hi,
Wondering what the typical struts approach is to
handling and passing back
errors to the user is. I'm not talking about
ActionForm validation, but
rather
I basically do the same thing as Paul. My business objects throw
their own exceptions, which I can catch. These exception classes
are chained and often include more than one message: the initial
cause and my business explanation. I use the ActionError class to
send this to the JSP. Since they
Thanks Ted Paul.
As always, a useful piece of the puzzle.
Just wondering what you need the isCause() method. I
read the article about exception handling, but when
you write the detail message -- won't this write the
cause out for you?
Where would you not have the cause?
Also: the business
Sometimes there is only a business exception, other times there is an
underlying exception followed by a business exception. So the business
object is thrown a SQL error, wraps it, and throws its own version.
Other times, there can be a business logic error that doesn't wrap
anything else.
Hi,
Wondering what the typical struts approach is to handling and passing back
errors to the user is. I'm not talking about ActionForm validation, but
rather the situation where an Action determines there is a error (ie either
directly itself or via an exception from a business object).
]]
Sent: Wednesday, 28 November 2001 1:41 PM
To: [EMAIL PROTECTED]
Subject: Struts Error Page Approach - Recommended / Struts Support
Hi,
Wondering what the typical struts approach is to handling and passing back
errors to the user is. I'm not talking about ActionForm validation, but
rather
.
How is everyone else handling it?
- Paul
- Original Message -
From: Greg Callaghan [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, November 28, 2001 1:40 PM
Subject: Struts Error Page Approach - Recommended / Struts Support
Hi,
Wondering what the typical struts approach
7 matches
Mail list logo
