|
|
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
Exceptions Management |
|||||||||||||||||||||||||
The API cross references give an immediate access to relevant interfaces and classes. |
|||||||||||||||||||||||||
ErrorsAn error indicates serious problems that an application should not try to catch. |
|||||||||||||||||||||||||
ExceptionsAn exception indicates problems that an application might want to catch. |
|||||||||||||||||||||||||
Error HandlerAn error handler implements a chain of responsibility to deal with bug report and warning. Each member of the chain knows how to access its successor and how to handle a request. This scheme is a flexible way to adapt error management to a specific application. The default error handler reports bugs by throwing an error and writes warning on the standard error output stream. In the case of a broken chain of responsability, we delegate the request to the DefaultErrorHandler class variable. Here is the reason we do not rely on exception to propagate errors. |
|||||||||||||||||||||||||
API Cross References
| |||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|