> Since we should keep the necessity of try/catch to a minimum, I > figure people can live with a RuntimeException potentially being > thrown until we can get true multicast functionality in.
So the person calls the method, and because they are saving themselves from the perils of exception handling, their method fails. Not only that, but it silently fails all the way up the stack until someone catches Throwable, or they blow out the thread. Which reminds me ... Avalon's thread runners catches Throwable and silently discards errors. Seems to me that it would be better if Avalon had a log for things not caught by application components, and used it. See: http://cvs.apache.org/viewcvs/avalon-excalibur/thread/src/java/org/apache/ex calibur/thread/impl/WorkerThread.java?rev=1.3&content-type=text/vnd.viewcvs- markup --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
