In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com




SOAP Compliance Limitations
The QDoc message envelope has the following limitations and qualifications:
The QDoc solution supports document-style message exchange as opposed to SOAP RPC. In order to make support for SOAP RPC and related standards such as WSDL easier to implement in future releases, SOAP encoding rules are used to represent all QDoc data.
Note: The above limitation applies to the QDoc 1.0 specification only. The QDoc 1.1 specification does not use SOAP encoding rules.
All QDoc messages require a Header element, whereas SOAP considers this element optional.
QAD applications ignore the role attribute on all SOAP 1.0 header blocks—or the actor attribute in SOAP 1.1 headers—acting as the ultimate SOAP receiver in all cases. In other words, a QAD application automatically plays all roles that appear in the SOAP message.
QAD applications ignore the mustUnderstand attribute on all SOAP header blocks, assuming that it must understand and process every received QDoc. In other words, they always act as if mustUnderstand is set to true (for SOAP 1.0) or 1 (for SOAP 1.1).
QAD applications cannot act as SOAP intermediaries, passing the QDoc to other SOAP nodes for processing. Rather, they process all inbound messages as the ultimate receiver.
QAD applications process a received QDoc only once, regardless of the number of SOAP header blocks that may be included inside the Header element of the envelope.