On Wed, Jan 27, 2010 at 9:25 AM, Dale Newfield wrote:
>
> P.S.:
> Patient: Doctor, doctor! It hurts when I do *this*.
> Doctor: Stop doing that.
>
>
>
Hopefully *this* isn't something like "walking" ;)
CRANFORD, CHRIS wrote:
That doesn't solve my original problem Gabriel.
It does if you are not tied to using chaining, which is almost always a
bad idea. Why isn't this implemented simply as an interceptor?
-Dale
P.S.:
Patient: Doctor, doctor! It hurts when I do *this*.
Doctor: Stop doin
t; Chris
>
>
> -Original Message-
> From: Gabriel Belingueres [mailto:belingue...@gmail.com]
> Sent: Tuesday, January 26, 2010 8:06 PM
> To: Struts Users Mailing List
> Subject: Re: Chain Getting Original URI
>
> (I found the chain result type somewhat problematic, so I
PM
To: Struts Users Mailing List
Subject: Re: Chain Getting Original URI
(I found the chain result type somewhat problematic, so I avoid it
every time I can.)
Having said that, if your action ONLY captures the exception, log it,
email it and then forward the output to an error.jsp page, AND you are
(I found the chain result type somewhat problematic, so I avoid it
every time I can.)
Having said that, if your action ONLY captures the exception, log it,
email it and then forward the output to an error.jsp page, AND you are
using Log4J you may find useful to attach more than one appender to
the
Our Struts2 application has java.lang.Exception mapped to a global
result called 'error'. Our 'error' global result is setup as a CHAIN
type to send the user to our ExceptionHandlerAction. This action is
designed to capture the exception, log it, email it to an administration
mailbox and then fo
6 matches
Mail list logo
