Thanks for the feedback to both of you!
Subclassing the ServletException is actually what I wanted to avoid. I consider
that a hack, if the new exception I'm creating doesn't have anything to do with
a Servlet (a UserNotAuthorizedException for instance shouldn't have to inherit
from ServletExc
> -Original Message-
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: 10 June 2001 02:00
> To: [EMAIL PROTECTED]
> Subject: Re: Exception handling in the ActionServlet
>
>
>
>
> On Sat, 9 Jun 2001 [EMAIL PROTECTED] wrote:
>
> >
On Sat, 9 Jun 2001 [EMAIL PROTECTED] wrote:
> Hi,
>
> I would like to catch all of our project specific exceptions in one place (as a
> last resort, if nobody else catches them earlier on) and handle them in a
> generic way. The obvious way to do this, I think, is by overriding
> processAct
3 matches
Mail list logo
