XFA Specification
Chapter 11, Forms That Initiate Interactions with Servers
Using Web Services
335
<soap:Fault>
<faultcode>...</faultcode>
<faultstring>...</faultstring>
</soap:Fault>
</soap:Body>
The
soap:Fault
element can also contain a
faultactor
element but this is uncommon.
Definition file may define multiple individual operations, each using a different connection set
The service defined by this definition file can include many individual operations. However a
wsdlConnection
element describes just one operation. Hence it may require many
wsdlConnection
elements to fully describe a service.
The simple service in this example supports a single operation, so in this case only one
wsdlConnection
element is needed.
Example 11.2 Complete connection set packet
<connectionSet
xmlns="http://www.xfa.org/schema/xfa-connection-set/2.4/">
<wsdlConnection
dataDescription="DataConnectionTradePriceRequestDD"
name="TradePriceWS">
<wsdlAddress>
http://example.com/stockquote.wsdl
</wsdlAddress>
<soapAction>
http://example.com/GetLastTradePrice
</soapAction>
<soapAddress>
http://example.com/StockQuote
</soapAddress>
<operation input="GetLastTradePriceInput"
output="GetLastTradePriceOutput">
TradePriceRequest
</operation>
</wsdlConnection>
</connectionSet>
The
wsdlConnection
element has attributes (below) that link it to other parts of the XDP.
●
dataDescription
attribute points to a data description that must be created (“Data
name
attribute supplies a name for this connection that is used in
connect
elements to indicate that
the content of a field, exclusion group, or subform takes part in the transaction (“Connection
●
The
wsdlAddress
child of the
wsdlConnection
element contains the URL of the WSDL service
definition. This is optional information for the use of form creation tools. In this case, its location happens
to be the same as its namespace, but it could be anywhere.
The
soapAction
child of
wsdlConnection
is copied from the
soapAction
attribute of the
soap:operation
element in the WSDL definition file. In this case
soapAction
is empty because in the
WSDL definition file the value of the attribute is the null string.