XFA Specification
Chapter 11, Forms That Initiate Interactions with Servers
Using Web Services
332
xmlns:dd="http://ns.adobe.com/data-description/"
dd:name="dataDescriptionName">
<connectionName>
<soap:Header
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
... data description for header ...
</soap:Header>
<soap:Body
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
... data description for message ...
</soap:Body>
</connectionName>
</dd:dataDescription>
Note:
There can only be one
connectionName
element per data description. Note also that the
connectionName
element's namespace is ignored.
For example, the following data description declares the message schema to use with a web service
connection called
POConnection
:
<dd:dataDescription
xmlns:dd="http://ns.adobe.com/data-description/"
dd:name="ExampleSoapInfo">
<POConnection>
<soap:Body
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<po1:orderItem
xmlns:po1="http://www.example.com/po1">
<po1:OrderId/>
<po1:Description dd:minOccur="0"/>
<po1:Quantity/>
</po1:orderItem>
</soap:Body>
</POConnection>
</dd:dataDescription>
In the above example, the
soap:Body
element contains the schema for the message. The optional
soap:Header
element has been omitted.
Example That Illustrates the Web Services Architecture
The best way to understand this architecture is to go through an example. This example uses a simple
stock-quote service. In order to use the service the client sends a message to the server containing a
header and a ticker symbol. The server replies with a message containing status information and, if the
query is successful, the current stock price.
This example is borrowed from the WSDL 1.1 specification [WSDL1.1].
Example 11.1 Web service description file
1 <?xml version="1.0"?>
2 <definitions name="StockQuote"
3
targetNamespace="http://example.com/stockquote.wsdl"
4
xmlns:tns="http://example.com/stockquote.wsdl"
5
xmlns:xsd1="http://example.com/stockquote.xsd"