HOME       >>       Programming

How Are You Using The Soap Header?


I was seeking the W3C schools forum, but as you can see in another thread, it's down. I hope this question fits in the HTML,XML domain enough. (please let me know if another is more appropriate) There's a debate going on within my company and I'm seeking outside opinions.We're building web services for internal use, for communication between applications. Initially we were not using SOAP at all. Our services were delivered by MQ. Within the payload of these messages, we established a "header", which gives some context to the service (transactionID, sourceID, DestinationID), and had some exception handling.Now that we've moved to SOAP, we're using the fault constructs, outside of our payload for exceptions.There is a camp that believes that we should move the context information out of the body and into the SOAP header. The argument is that the payload should only contain business objects. Anything "systemy" belongs in the header.There's another camp that says the context has to remain in the body, because there are some circumstances where the header will have been stripped off from the body, and the consumer will still need the context information.I tend to agree with the use-the-header camp in principle. But I have difficulty with the details. SOAP header is an "any" that depends on the use of some other schema to define its contents. There seems to be a sea of cryptically explains SOAP header extensions. I'm at a loss to know which ones I should consider using or how to map our existing context data to them. Anyone else out there facing this dilemma?BTW. other that W3C schools, are there good forums for web services out there?


Xisto.com offers Free Web Hosting to its Members for their participation in this Community. We moderate all content posted here but we cannot warrant full correctness of all content. While using this site, you agree to have read and accepted our terms of use, cookie and privacy policy. Copyright 2001-2019 by Xisto Corporation. All Rights Reserved.