Q

Sending an XML construct as a 'Document literal' message type

Given that I have a working client-server SOAP exchange (via MSSOAPP toolkit 3.0), what are the changes I need to make to send an XML order construct as a 'Document literal' message type? I am having difficulty interpreting the specification. I also have been unsuccessful in locating any working examples.
The specification can be difficult to interpret and unfortunately other than the "stock quote" example there are almost no other working samples publicly available. In general, it appears that Microsoft at present has the furthest developed solutions to allow "document/literal" messages. In particular, for WSDL definitions, make sure that the SOAP binding set to "document", SOAP body set to "literal". The actual "document/literal" SOAP request has basically similar content as the "rpc" request. The main difference is how the service is referred to. The following links are great presentations on that very subject:

http://www.microsoft.com/usa/presentations/Under_the_HoodwithNETWebServices.ppt
http://msdn.microsoft.com/library/en-us/soap/htm/soap_overview_7lps.asp
This was first published in December 2003

Dig deeper on XML and XML schema

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

SearchSoftwareQuality

SearchCloudApplications

SearchAWS

TheServerSide

SearchWinDevelopment

Close