Whenever the client requests a service form the server the response to this request will include a (possibly empty) list of server feedback messages. These messages can give detailed information about the processing of the request and are meant to provide feedback for the human reader.
E.g. if a user requests to list all features that are member of a view but the view definition is not valid the response from the server would be an empty list of features and a server feedback message that indicates that the list is empty because of an invalid view definition.
Each server feedback message consists of a timestamp when the message was created, a feedback code, a message text (expressed in the current session's language) and a severity. Severity levels used in server feedback messages are listed in table 1.
A server feedback message can contain an action log that may provides more detailed information.
Severity |
Usage |
Informational |
Used for feedback messages that are possibly of interest to the user. The message but has no immediate effects on the result of the request |
Warning |
Used if during processing the Application Server detected a condition that is influencing the result of the request in a way not intended by the user, or for conditions that will likely influence future requests |
Severe |
Used if during processing a condition was detected that hinders the Application Server from fulfilling the request. |
Table 1: Server feedback message severities
