Re: Extending DynaValidatorActionForm... or using something else?

[Eddie Bush]

Application-specific exceptions are one of the least used and most useful 
tools.  That's exactly how I'd go about doing it, and I dare say it's the 
right way.

----- Original Message ----- 
From: "Laurent Duperval" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 18, 2004 1:42 PM
Subject: Re: Extending DynaValidatorActionForm... or using something else?


Laurent Duperval wrote:
I'm sure others have done something similar. What approaches have you 
taken?

Well, shortly after posting this, I remembered the <exception> tag could 
be added in an action. By defining a specific exception for the errors I'm 
trackin and sending them back to the container, this seems to fit the 
bill. There's still a couple of minor issues, but I think this might be 
sufficient.

L 

---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0442-3, 10/15/2004
Tested on: 10/18/2004 7:06:26 PM
avast! - copyright (c) 2000-2004 ALWIL Software.
http://www.avast.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]