The Bridge features an implicit error handling mechanism. If an error occurs during the execution of a service and if the error is not caught, it is sent back to the client. The mechanism to do this depends on the service type.
|
|
<your example path>\Basic Modeling\ErrorHandling\uml\errorHandling.xml |
Every error is described using four classifiers:
|
Classifier |
Description |
Values |
|
|---|---|---|---|
|
Category |
Specifies the category of the error. Category can be either "Internal", "External," or "User". |
Internal |
Internal errors occur for example if NULL values are used as input for operations that cannot handle such values. |
|
External |
External errors occur when communicating with the environment. For example, the Bridge cannot connect a backend system (e.g. a database connection error) or – for instance – a SOAP input message leads to an XML parsing error because the request sent to the Bridge is not a valid SOAP request. |
||
|
User |
User errors are defined in the UML model. |
||
|
Domain
|
Specifies an internal group information token, e.g. all SOAP adapter errors are grouped under the domain SOAPADSM (a list of all built-in error domains can be found in Error Codes). |
e.g. BESM |
|
|
Code |
Specifies the number of the error. Together with the domain value it is the unique identifier of an error (a list of all built-in error domains can be found in Error Codespp.). |
1 |
|
|
Description |
Contains a human readable description of the error. |
Function did not return data. |
|