What good would a runtime exception do me at that point? The method interceptor which contains that code is executing the method invocation in another thread using an Executor (JDK5). So, the runtime exception wouldn't get back to the caller. At best it would probably just get printed to standard error or something. That's why I chose to actually log the error in the first place.
-----Original Message----- From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED] Sent: Friday, September 09, 2005 2:49 AM To: commons-dev@jakarta.apache.org Subject: Re: [proxy] Commons-Lang Dependency... Rahul Akolkar <[EMAIL PROTECTED]> writes: ><snap/> >- getLog().error( "Method invocation threw an exception.", t ); >+ // What to do here? I can't convey the failure back to the caller. ><snip/> throw new RuntimeException(t) if you aim for JDK 1.4+ throw new RuntimeException(t.getMessage()) if you need 1.3 compatibility. should be possible everywhere. Best regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/ RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire Linux, Java, perl, Solaris -- Consulting, Training, Development 4 - 8 - 15 - 16 - 23 - 42 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
