See below:
> -Original Message-
> From: Michal Mosiewicz [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 16, 2003 2:12 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [OS-webwork] XWorkException extending RuntimeException
>
>
>
> - Original Message --
- Original Message -
From: "Jason Carreira" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 16, 2003 5:16 PM
Subject: RE: [OS-webwork] XWorkException extending RuntimeException
> The point of this is that where the exceptions are generated
Title: RES: [OS-webwork] XWorkException extending RuntimeException
This may sound a bit obvious, but I'm not a fan of checked exceptions for *unrecoverable* situations either. I do, instead, firmly believe in the fail-fast principle: any situation that can't be recovered demands
coverable
situations.
Jason
-Original Message-
From: Michal Mosiewicz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 3:46 PM
To: opensymphony-webwork
Subject: [OS-webwork] XWorkException extending RuntimeException
I've noticed some code in xwork that is probably to deal with O
Mosiewicz
Sent: Wednesday, October 15, 2003 12:46 PM
To: opensymphony-webwork
Subject: [OS-webwork] XWorkException extending RuntimeException
I've noticed some code in xwork that is probably to deal with OGNL
deficiencies in terms of proper exception handling. OGNL doesn't
contract
an
I've noticed some code in xwork that is probably to deal with OGNL
deficiencies in terms of proper exception handling. OGNL doesn't contract
any parsing exceptions and it seems they are added by means of
ParseException extending XWorkException that in turn extends
RuntimeException.
I don't think i
