Ultra Light Client Guide and Reference
A process in which an ExError exception occurs is
stopped. The context and UI associated with this process is no longer
functional. Custom handler code must relieve this situation by doing
one of the following:
- Terminate the context by sending #terminate to the
object answered by #ulcActiveContext. Use a forked
process to do this, because the exception-causing process might no longer be
functional.
- Resume the process by sending #resumeWith:
anObject to the Signal object. Do this only when the original
error is well understood and known to be resumable.
- Invoke default exception handling by sending #signal to
the Signal object.
If the handled exception disrupted the connection between application
server and UI, attempts to display messages on the UI will probably not
succeed.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]