Yeah, but I also delegate these exceptions to a handler that gives the user
options (quit the program, retry, email error, etc.). This takes place in the
proxy. It really would be elegant if I could consume the exception entirely, but
that isn't possible given the pattern.
jim
----- Original Message -----
From: "Rickard Öberg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 21, 2000 9:02 AM
Subject: Re: Using Dynamic Proxies for Fault Tolerance
On Mon, 21 Aug 2000 08:50:57 -0400, James Cook <[EMAIL PROTECTED]>
wrote:
>I agree, if three attempts fail I can try to get more agressive in my attempts.
>I suppose I'll just have to put a facade between the client and my wrappered
>(dyn. proxy) stub to eliminate the countless try/catch blocks.
Do remember that there are times when the call simply will not go
through no matter how many times you call it (for example if the db is
down). Then you have no other choice but to throw it to the caller.
Errors are only transparent in a perfect world.
Riddle me this:
Do we live in a perfect world?
/Rickard
--
Rickard Öberg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
