Re: [OS-webwork] Exception handler proposal

2003-11-03 Thread John Patterson
t;Jason Carreira" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, November 02, 2003 8:29 PM Subject: RE: [OS-webwork] Exception handler proposal I agree here.. If someone wants this, it can be implemented as an Interceptor anyway... > -Original Message- >

RE: [OS-webwork] Exception handler proposal

2003-11-03 Thread Fred Lamuette
ason Carreira Envoye : lundi 3 novembre 2003 01:12 A : [EMAIL PROTECTED] Objet : RE: [OS-webwork] Exception handler proposal I wish we could change the "throws Exception" but it's been there since before WW 1.0 and we decided early on to carry it forward to XW to allow a better path

RE: [OS-webwork] Exception handler proposal

2003-11-02 Thread Patrick Lightbody
bject: RE: [OS-webwork] Exception handler proposal I wish we could change the "throws Exception" but it's been there since before WW 1.0 and we decided early on to carry it forward to XW to allow a better path forward... > -Original Message- > From: Michal Mosiewic

RE: [OS-webwork] Exception handler proposal

2003-11-02 Thread Jason Carreira
er 02, 2003 5:25 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Exception handler proposal > > > >[...] > > Then wouldn't it be the invoker's responsibility, rather than the > >framework's? I'd say that exceptions should be delegated t

Re: [OS-webwork] Exception handler proposal

2003-11-02 Thread Hani Suleiman
Right on, reinventing wheels is fun for two kinds of people, the inventors, and those too blind to see existing wheels. On Nov 2, 2003, at 5:25 PM, MichaÅ Mosiewicz wrote: [...] Then wouldn't it be the invoker's responsibility, rather than the framework's? I'd say that exceptions should be deleg

Re: [OS-webwork] Exception handler proposal

2003-11-02 Thread Michał Mosiewicz
>[...] > Then wouldn't it be the invoker's responsibility, rather than the > framework's? I'd say that exceptions should be delegated to the most > responsible party, not the framework. Thus, the web app exception handler, > or the caller's, in the case of XWork's. I think this is a good point. I

RE: [OS-webwork] Exception handler proposal

2003-11-02 Thread Jason Carreira
I agree here.. If someone wants this, it can be implemented as an Interceptor anyway... > -Original Message- > From: Joseph Ottinger [mailto:[EMAIL PROTECTED] > Sent: Sunday, November 02, 2003 12:31 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Exception h

Re: [OS-webwork] Exception handler proposal

2003-11-02 Thread Joseph Ottinger
OTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Fred Lamuette > > Sent: Sunday, November 02, 2003 2:14 AM > > To: [EMAIL PROTECTED] > > Subject: RE: [OS-webwork] Exception handler proposal > > > > So a a generic exception handler like this one : > >

Re: [OS-webwork] Exception handler proposal

2003-11-02 Thread Francisco Hernandez
2003 2:14 AM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Exception handler proposal So a a generic exception handler like this one : could handle any exception and could do what you want. Cheers. Richard HALLLIER. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTEC

RE: [OS-webwork] Exception handler proposal

2003-11-02 Thread Patrick Lightbody
I still don't understand why using the Servlet's support isn't enough? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fred Lamuette Sent: Sunday, November 02, 2003 2:14 AM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Exception handler p

RE: [OS-webwork] Exception handler proposal

2003-11-02 Thread Fred Lamuette
ECTED] Objet : Re: [OS-webwork] Exception handler proposal It would be nice to be able to specify an error page based on URI pattern. eg any error that occurs with a uri matching "/action/flight*" gets forwarded/redirected to the action "flightError". - Original Message -

Re: [OS-webwork] Exception handler proposal

2003-11-01 Thread John Patterson
ED]> To: <[EMAIL PROTECTED]> Sent: Saturday, November 01, 2003 9:44 AM Subject: RE: [OS-webwork] Exception handler proposal > If this functionality exists it MUST be part of the webapp framework. As far > as I am concerned, I prefer a WW2-centric approach. In this viewpoint, yo

RE: [OS-webwork] Exception handler proposal

2003-11-01 Thread Fred Lamuette
:30 A : [EMAIL PROTECTED] Objet : Re: [OS-webwork] Exception handler proposal Err, why on earth would you want this in webwork? What's wrong with the exception handlers you can specify in web.xml, which work exactly as described below? On Oct 31, 2003, at 10:18 PM, Jason Carreira wrot

Re: [OS-webwork] Exception handler proposal

2003-10-31 Thread Francisco Hernandez
I was thinking of doing something just like this, i've got alot of boiler plate exception handling code in all my actions that i could get rid of by using something like this. Fred Lamuette wrote: Is there an exception handler mechanism in xwork ? Something like : that could redirect exceptions

Re: [OS-webwork] Exception handler proposal

2003-10-31 Thread Hani Suleiman
ssage- From: Fred Lamuette [mailto:[EMAIL PROTECTED] Sent: Friday, October 31, 2003 3:00 PM To: [EMAIL PROTECTED] Subject: [OS-webwork] Exception handler proposal Is there an exception handler mechanism in xwork ? Something like : that could redirect exceptions inherited from mypack.ApplicationExce

RE: [OS-webwork] Exception handler proposal

2003-10-31 Thread Jason Carreira
Nope... Interesting idea... Post a Jira issue for it... > -Original Message- > From: Fred Lamuette [mailto:[EMAIL PROTECTED] > Sent: Friday, October 31, 2003 3:00 PM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] Exception handler proposal > > > Is there an exc

[OS-webwork] Exception handler proposal

2003-10-31 Thread Fred Lamuette
Is there an exception handler mechanism in xwork ? Something like : that could redirect exceptions inherited from mypack.ApplicationException to the myExceptionHandlerAction action ? Cheers. Richard HALLIER Chef de projet [EMAIL PROTECTED] 01.40.12.41.52 www.uniclick.org UNICLICK