<reply> element |
  
|
<reply> element |
|
This element represents an interpretation of the server's reply interprocess message. It correlates the 'reply code', the first word (two bytes) of the message, to a type. The reply element determines how the server reply is converted from binary format to XML ("serialized").
Attributes
attribute name |
data type |
usage |
default value |
description |
|||
replyCode |
xsd:token |
optional |
* |
The range of values for the first word (2 bytes) of the server reply interprocess message that indicate that the specified type should be used to interpret the message. The value is a comma-separated list of ranges where range is 'lo:hi' and lo and hi are integers between -32768 and 32767. "*" may be used to represent the entire range. |
|||
type |
xsd:NCName |
required |
|
The name of <type>, defined in <types>, that describes the server reply interprocess message . |
|||
Remarks
When <replies> contains multiple <reply> elements, they are processed in document order. The first <reply> whose replyCode range includes the value server's reply code (the first 2 bytes of the reply message interpreted as a signed integer) is used.
Example
<replies>
<reply replyCode="0" type="MySuccessReply">
<mappings>
</mappings>
</reply>
<reply replyCode="-100:-1,1:100" type="MyWarningReply">
<mappings>
</mappings>
</reply>
<reply replyCode="*" type="MyErrorReply">
<mappings>
</mappings>
</reply>
</replies>