|
|
I've got two action behaviors called exception1 and exception2
that are supposed to catch exceptions. Unfortunately, the
exceptions are still displayed in passing, but too fast for you
to see them.
To see the problem, run the mortgage servlet, and into the "Principal"
field type an invalid character, such as an X (instead of a number).
The setPrincipal action uses the "Double.valueOf()" function to
try to convert this field into a number. If it fails, it should
generate an exception, which is caught by the exception1 action.
Unfortunately, the error dialog flashes up. To get the error
dialog to stay up, change the "Activate On" field of exception1
to parent.Exception.activateThenRethrow.
The same thing applies to the setInterest and exception2 actions.
** Wm 3/21/2000 **
Yes, this is a known problem. Exceptions are displayed as generated,
and therefore before they are caught. When caught, they are removed
from the error list, and so you briefly see the error window appear
when an exception is thrown and disappear when that exception is
caught.
ActivateThenRethrow will leave the dialog up because you trap
the exception in transit, but the final result keeps the error
around as if it wasn't caught at all.
** Philip 3/21/2000 **
Generated on: Mon Apr 10 11:49:40 PDT 2000