[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Manifest Element - Where located?
I disagree here... we had made the decision in Vancouver to put data in the BODY, and routing type info in the header... it seemed like a nice logical split that SOAP gives us that we didn't have before. The Manifest is a logical representation of the payload, which is the "body" of the message. So the manifest should go into the SOAP-ENV:BODY. Otherwise, we will ALWAYS have an empty SOAP-ENV:BODY, (since it is required). The reworked placement of the elements fell quite nicely into this updated structure. -----Original Message----- From: Miller, Robert (GXS) [mailto:Robert.Miller@gxs.ge.com] Sent: Monday, February 26, 2001 8:29 AM To: firstname.lastname@example.org Subject: Manifest Element - Where located? Hi All, I seem to recall that the Manifest element was to be placed in the SOAP-ENV:Body. IMO, it belongs in the SOAP-ENV:Header area. From "SOAP Messages with Attachments" http://msdn.microsoft.com/xml/general/soapattachspec.asp Introduction, last two sentences of paragraph 2: "More rigorous semantics for message packages requires a new entity type. Such a type can be built by extending the approach described here with a new SOAP header entry which, for instance, may be used to provide a manifest of the complete contents of the message package." Seems clear to me - put the Manifest in the SOAP-ENV:Header! Of course, within the ebXML payload, there may also be imbedded pointers to message attachments. The first example in "SOAP Messages with Attachments" gives one such example for an auto claim form application. Such 'application' references are of course unrelated to the ebXML Manifest references. FYI, I'm not convinced that any part of the pre=SOAP ebXML header should migrate to the SOAP-ENV:Body. IMO, all of the ebXML Header stuff should resdie in the SOAP-ENV:Header. Cheers, Bob ------------------------------------------------------------------ To unsubscribe from this elist send a message with the single word "unsubscribe" in the body to: email@example.com
Powered by eList eXpress LLC