- From: Jacek Kopecky <jacek@systinet.com>
- Date: 14 May 2003 19:29:20 +0200
- To: "Burdett, David" <david.burdett@commerceone.com>
- Cc: "XML Dist-App (E-mail)" <xml-dist-app@w3.org>
David, this is a bigger issue of XML not being able to carry XML inside. If you want to carry XML documents inside any XML, a solution is to treat the document as opaque binary data and so base64 is a viable course. It doesn't seem you're missing anything, but your problem is just a greater one that SOAP doesn't attempt to solve. Best regards, Jacek Kopecky Senior Architect Systinet Corporation http://www.systinet.com/ On Tue, 2003-05-13 at 18:49, Burdett, David wrote: > I'm reposting this question as I did not get any response earlier. > > The SOAP PR spec [1] states a SOAP message must not contain > information that often goes in the XML Prolog such as: document type > declarations, processing instructions or comments before the main > document element. > > A question. What should you do if the XML that you want to transport > was originally a complete XML document (perhaps digitally signed) that > contains this type of information and you want this information to be > preserved when the document reaces the ultimate destination so that it > can be used? > > My reading of the current SOAP spec suggests that this is not possible > unless you Base64 encode it ... or am I missing something. > > David > PS I realise this may have been already discussed but I missed it. > > [1] http://www.w3.org/TR/soap12-part1/#soapenv
Received on Wednesday, 14 May 2003 13:29:32 UTC