Name: rl43681			Date: 07/26/2003


A DESCRIPTION OF THE REQUEST :
example the code in EventHandler.invoke.
It simply prints stack traces and returns null.

JUSTIFICATION :
1) This defeats any exception handling mechanisms with a more global context; a ThreadGroup handler, AWT EventDispatchThread handler, or simply a try/catch block already on the stack.  This makes a very useful class unusable for production code.

2) It violates Java best practices on exception handling



EXPECTED VERSUS ACTUAL BEHAVIOR :
It should simply rethrow unchecked exceptions and wrap any checked exceptions in an RTE wrapper.

<pre>
try {
   ....
} catch (RuntimeException rte) {
    throw rte;
} catch (InvocationTargetException ex) {
    throw new RuntimeException(getTargetException());
} catch (Throwable t) {
    throw new RuntimeException(t);
}
</pre>
Exception thrown by application code is smothered and simply printed on stdout.

---------- BEGIN SOURCE ----------
This is a no-brainer issue.
If you really need an example drop me a mail note.

---------- END SOURCE ----------

CUSTOMER SUBMITTED WORKAROUND :
subclass EventHandler properly implementing invoke and use that class instead :(
(Incident Review ID: 183039) 
======================================================================