Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Development" <avalon-dev@jakarta.apache.org>
Message-Id: <5.1.0.14.0.20011019115758.01bea108@pop>
Date: Fri, 19 Oct 2001 12:02:17 -0400
To: "Avalon Development" <avalon-dev@jakarta.apache.org>
From: Peter Royal <proyal@managingpartners.com>
Subject: Re: DynamicProxy replacement.
In-Reply-To: <3BD04A30.2050606@yahoo.com>
References: <5.1.0.14.0.20011019104955.01b967a8@pop>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 04:43 PM 10/19/2001 +0100, you wrote:
>>It would be very nice to be able to catch the exceptions that are 
>>actually thrown. How do other users of phoenix deal with this problem? If 
>>I have a service that throws a checked exception, the client of that 
>>service has to handle it properly, but the handling code is never called 
>>because the original exception never comes through, its the wrapped one.
>
>You can ask the InvokationTargetException what exception it contains. You 
>just have to code in such a way that you know a proxy exists.

(forgive my naivety here...) but why do we have these proxies in the first 
place? If I the block author is using a service that throws a checked 
exception, why should I have to trap the checked exception *AND* an 
InvocationTargetException and check to see if its contained exception is 
the one i'm trapping? That seems to be a burden to me.
-pete


-- 
peter royal -> proyal@managingpartners.com
managing partners, inc. -> http://www.managingpartners.com


---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org