RE: Manifest Element - Where located? - 2

["Burdett, David" <david.burdett@commerceone.com>]

Bob

You said ... "Put the ebXML conformant XML message in the SOAP-ENV:Body."

The difficulty of doing this is what caused the TRP group to not do SOAP
last spring. Specifically, you can't put a **complete** XML document inside
a SOAP body as you have to  remove the prolog. This causes problems if the
XML document had been previously signed e.g. using XML DSig and including
the prolog. With your suggestion you have to remove the prolog and therefore
break the signature.

The real issue is whether data ebXML will allow additional data to be put in
the body.

The general consensus seems to be that we do not which means we should flag
an error if any data is there. I concur.

David


-----Original Message-----
From: Miller, Robert (GXS) [mailto:Robert.Miller@gxs.ge.com]
Sent: Tuesday, February 27, 2001 7:44 AM
To: ebXML Transport Mailing List
Subject: RE: Manifest Element - Where located? - 2


Good people,

Rik says keep it simple.  I agree.  I say simple is this:

1) Put ALL of the ebXML header stuff in the SOAP-ENV:Header (where it
belongs).
	Some here, some there is NOT simple
   
2) Put the ebXML conformant XML message in the SOAP-ENV:Body.  If no such
body is present for the message, the SOAP-ENV-Body is empty (or perhaps
someday, not present.
	ebXML messages are always in the same place.
	
3) If there are attachments, the attachments are not ebXML messages, they
are just attachments.
	
Cheers,
        Bob

------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-transport-request@lists.ebxml.org