semi合集-English.pdf - 第3274页
SEMI E128-0304 © SEMI 2003, 2004 8 6.6.4 Example Reply Messa ge for a Bad Request — In Figu r e 5, a faultc ode value of “SOAP-ENV:Client” indicates that the error w as caused by bad form at or data in the reques t messa…
SEMI E128-0304 © SEMI 2003, 2004 7
6.6.3 Example Successful Reply Message — The message example shown in Figure 4 illustrates the completed
MessageHeader for a reply message from a server to a client with a response to a prior request message. This
example represents a reply to the request message in the previous example. The CorrelationId of “7” serves to
associate this reply with the RequestId of the earlier request message.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<MessageHeader xmlns="urn:semi-org:schema:xmlmsg:0:0"
elementFormDefault="qualified">
<From>EQ99</From>
<To>EqHost</To>
<MessageType>REPLY</MessageType>
<CorrelationId>7</CorrelationId>
<Action>dataRequest</Action>
</MessageHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<data>
<DATAID type="ASC">420</DATAID>
<CEID type="ASC">GAS</CEID>
<DATASETS type="LIST">
<DATASET>
</DATASET>
</DATASETS>
</data>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Figure 4
Reply Message (Successful) Example
SEMI E128-0304 © SEMI 2003, 2004 8
6.6.4 Example Reply Message for a Bad Request — In Figure 5, a faultcode value of “SOAP-ENV:Client” indicates
that the error was caused by bad format or data in the request message from the client.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<MessageHeader xmlns="urn:semi-org:schema:xmlmsg:0:0"
elementFormDefault="qualified">
<From>EQ99</From>
<To>EqHost</To>
<MessageType>REPLY</MessageType>
<CorrelationId>7</CorrelationId>
<Action>dataRequest</Action>
</MessageHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>BadSyntax</faultstring>
<detail>DATAID not found in request.</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Envelope>
Figure 5
Reply Message (Bad Request) Example
6.6.5 Example Reply Message for a Processing Error — In Figure 6, a faultcode value of “SOAP-ENV:Server”
indicates that the error occurred during processing of the message. The request message was complete and valid to
allow the server to begin processing, but some occurrence prevented successful completion of the action requested
by the client.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<MessageHeader xmlns="urn:semi-org:schema:xmlmsg:0:0"
elementFormDefault="qualified">
<From>EQ99</From>
<To>EqHost</To>
<MessageType>REPLY</MessageType>
<CorrelationId>7</CorrelationId>
<Action>dataRequest</Action>
</MessageHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>IdNotFound</faultstring>
<detail>DATAID requested not known to tool.</detail>
</SOAP-ENV:Fault> </SOAP-ENV:Body>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Figure 6
Reply Message (Processing Error) Example
SEMI E128-0304 © SEMI 2003, 2004 9
6.6.6 Example Callback Message for a Variable Number of Events — Figure 7 shows a callback message from a
server to a client. The callback delivers some additional data related to a prior request message. The CorrelationId
“8” allows the client to correlate the callback with a prior request message. This callback uses the EventIndex
element to convey that this callback is the third of a variable number of callbacks. When the value of Finished is
“true” then the client will know not to expect any further callback messages with this CorrelationId.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<MessageHeader xmlns="urn:semi-org:schema:xmlmsg:0:0"
elementFormDefault="qualified">
<From>EQ99</From>
<To>EqHost</To>
<MessageType>CALLBACK</MessageType>
<CorrelationId>8</CorrelationId>
<Action>dataSubscribe</Action>
<EventIndex>
<Position>3</Position>
<Finished>false</Finished>
</EventIndex>
</MessageHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<data>
<DATAID type="ASC">420</DATAID>
<CEID type="ASC">GAS</CEID>
<DATASETS type="LIST">
<DATASET>
<DSID>A</DSID>
<DVS>
<DV>
<NAME>ARGON</NAME>
<VAL>156</VAL>
</DV>
</DVS>
</DATASET>
<DATASET>
<DSID>B</DSID>
<DVS>
<DV>
<NAME>ARGON</NAME>
<VAL>67</VAL>
</DV>
</DVS>
</DATASET>
</DATASETS>
</data>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Figure 7
Callback Message (Variable Number of Events) Example