On Fri, 24 Oct 2003, Craig R. McClanahan wrote: <snip /> > I agree that we would need the exception class, but why do we need > anything other than the standard handler (o.a.s.c.ExceptionCatcher)? It > fires off an exception handling chain, and the default handler there > already looks at your <exception> settings in struts-config.xml to > figure out what to do for any arbitrary exception class. It's up to the > app to handle UnauthorizedException however it wants, just like it's up > to the app to handle an SQLException (or any other type, for that > matter) returned from an Action. > > While we're at it, there are a few other places where Struts 1.1 returns > an HTTP error; they should be evaluated for being treated the same way > in a chain-based request processor.
That works for me - I was under the assumption 100% backwards compatibility was the goal (i.e. drop-in replacement). I'll write it up. Don --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
