semi合集-English.pdf - 第3273页
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 t o a clie nt with a response to…
SEMI E128-0304 © SEMI 2003, 2004 6
6.5.1.3 faultstring — The faultstring element shall be present to describe the cause of the fault in human
understandable text.
6.5.1.4 faultactor — The use of the faultactor element is optional.
6.5.1.5 detail — The detail element is optional. It may be used to describe the cause of a fault that resulted from
processing the body of the request message.
6.6 XML Message Examples — The examples of XML messages presented in this section are intended to help the
reader understand the structure of messages that conform to this specification.
6.6.1 Example SOAP Envelope — The SOAP envelope illustrated in Figure 2 contains the required Header and
Body elements. It also includes the MessageHeader element specified in this standard. The contents of these
elements are intentionally left empty in this example.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<MessageHeader>
</MessageHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<PayloadData>
</PayloadData>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Figure 2
SOAP Envelope
6.6.2 Example Request Message — The message example shown in Figure 3 illustrates the completed
MessageHeader for a message from a client to a server to request a service. In this example, the SOAP Body
contains an element that identifies the data that is being requested with the Action “dataRequest.” The RequestId
assigned by the client is “7.” The client will expect a reply message that contains “7” in the 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>EqHost</From>
<To>EQ99</To>
<MessageType>REQUEST</MessageType>
<RequestId>7</RequestId>
<Action>dataRequest</Action>
<ReplyExpected>true</ReplyExpected>
</MessageHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<data>
<DATAID type="ASC">420</DATAID>
</data>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Figure 3
Request Message Example
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