The <Event> Element

Description

Events and errors occurred during the processing of the request. These messages are mainly informational, and could be checked in case of problems like missing data. See also Trappable Events for a list of events you can check in an automated fashion.

<Event
    number = integer
    severity = "literal"
    group = "literal"
    type = "literal"
    debug-only = boolean >
</Event>

Content

Content type: text

Attributes

Attribute nameData typeDescription
numberinteger Indicates the nuber of the event; see also Trappable Events. Next to severity, this is an attribute you could inspect.
severityliteral Indicates the severity of the event; the possible severities of events are:

informational Informational events; indicates no problem, but rather progress information of the TBXDS engine.
nominal Noteable, but not severe; these events could be checked for debug purposes (see also <Parameter>).
critical This is usually bad; in case of suspected missing data, you should check these events.
fatal This is very bad; it means that the TBXDS got into some trouble while processing your request, and was not able to save itself. The TBXDS will try to send you all data it could gather, but usually some (if not all) data is missing.

groupliteral Indicates in which layer of the TBXDS engine the event was thrown. This attribute is purely informational.
typeliteral Indicates to which category this event belongs; usually "general" is returned. This attribute is purely informational.
debug-onlyboolean The debug-only attribute only occurs when the TBXDS engine has been set to not optimize the XML tree, and to emit full debug information (see <Parameter>).

Number of occurences

Unlimited

Occurs within

<MetaData>

Can contain

None (element is closed).

See also

Trappable Events