Error Messages: Unterschied zwischen den Versionen

Aus DRV STRING
Wechseln zu: Navigation, Suche
 
(2 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 4: Zeile 4:
  
 
Errors on the outer level include cases like unavailable operators or invalid content. They are not version-specific.
 
Errors on the outer level include cases like unavailable operators or invalid content. They are not version-specific.
 +
 +
<syntaxhighlight lang="xml">include example here</syntaxhighlight>
  
 
== Errors in Content/Payload ==
 
== Errors in Content/Payload ==
  
 
Errors related to valid requests might be handled "inline" in the matching response if the operator is able to create a response, otherwise an ErrorResponse may be used (<GeneralErrorType> in StringError.xsd).
 
Errors related to valid requests might be handled "inline" in the matching response if the operator is able to create a response, otherwise an ErrorResponse may be used (<GeneralErrorType> in StringError.xsd).
 +
 +
<syntaxhighlight lang="xml">include example here</syntaxhighlight>
  
 
== Errors in Responses ==
 
== Errors in Responses ==
  
The response types have their own error fields for informational messages and non-fatal errors. See the documentation of the [[Documentation|request/response types]].
+
The response types have their own error fields for informational messages and non-fatal errors. See the documentation of the [[Documentation|queries by category]].
 +
 
 +
<syntaxhighlight lang="xml">include example here</syntaxhighlight>
 +
 
 +
== Standard Error Messages ==
 +
 
 +
STRING defines a set of standard error messages and matching codes. They are not stored in the XSD schemata but on the STRING web server: [http://string.drv.de/message/ http://string.drv.de/message/errors_$LANG.csv]. We will supply at least English and German versions of these files; other languages might follow later.

Aktuelle Version vom 17. Oktober 2019, 10:09 Uhr

Error messages can be sent on three different levels.

Errors in StringMessage

Errors on the outer level include cases like unavailable operators or invalid content. They are not version-specific.

include example here

Errors in Content/Payload

Errors related to valid requests might be handled "inline" in the matching response if the operator is able to create a response, otherwise an ErrorResponse may be used (<GeneralErrorType> in StringError.xsd).

include example here

Errors in Responses

The response types have their own error fields for informational messages and non-fatal errors. See the documentation of the queries by category.

include example here

Standard Error Messages

STRING defines a set of standard error messages and matching codes. They are not stored in the XSD schemata but on the STRING web server: http://string.drv.de/message/errors_$LANG.csv. We will supply at least English and German versions of these files; other languages might follow later.