Scott Rubin wrote:
> Hello again,
> 
> While I wait for SOAP/SSL to be implemented I have another problem.  I 
> have a web service running with many clients.  The way it is set up is 
> that through a web interface the admin will change the configurations of 
> the clients.  The clients will all have XML documents stored locally 
> containing their settings.  When changes are made the web service will 
> send a new version of that XML document to the client VIA soap.  My 
> problem is that I can't seem to embed the XML document into the SOAP 
> envelope and have it work on the other end.  Many sites on the net say 
> to use a SOAP attachment, but this wont work for our purposes.

I'm not a big fan of SOAP; too complicated for my tastes, and, as I 
recall, there are a few restrictions on what you may include as content. 
    For example, you may not include an XML doc that has a DOCTYPE 
declaration.  It breaks SOAP.  (But check this; it's been a while since 
I did any serious research on SOAP.  I tend to prefer XML-RPC)

You could perhaps base64 encode the XML package and send it as "simple" 
string, then decode it at the client.  Or it may be possible to wrap the 
payload doc in a CDATA section (but watch that the payload itself 
doesn't contain CDATA sections).



James