ansaurus

Question

Getting quotes in innerXML to go on the wire as "

Answer 1

A:

You need to get that string into the SOAP message as a CDATA section, so that you can format it exactly as you want, and so that WCF doesn't touch it.

The problem you have at the moment is that the service is expecting an encoding that somewhere between xml and html - which is therefore not nicely handled by format that the Soap formatter is using - so you are always going to have to escape the quotes yourself.

I have a hunch, though, that if you surround it in the CDATA tags <![CDATA[*yourstring*]]> in your string parameter, the markup for that will be escaped over the wire and reach the other end as <![[*yourstring-XML-element-encoded*]]>

If that's the case, what you could do is to alter the code that was generated automatically by the VS service reference generator so that the parameter type of the method call on the proxy accepts a type that is basically the same as a string, but serializes itself as a CDATA section. Such a type is provided based on code written by Marc Gravell to answer another question here. The problem with doing this will be that if anyone uses the 'Update Reference' command in VS on that service reference, any changes you make will be lost.

So, instead, generate the reference with the svcutil command line utility (contrary to popular belief, VS doesn't use this tool - which is a shame because it is more flexible), import the config and code it generates into your project manually and get rid of the 'service reference'. That way, the code is yours to hack however you want, and you can easily see it in the project tree in VS.

Andras Zoltan 2010-01-26 09:59:41

I did try surrounding the quote `"` with the cdata bit. Unfortunately, even that wasn't respected. Here's what went out on the wire:`<SEARCHINFO-LIST><SEARCH_INFO action=<``![CDATA[]]>add<![CDATA[ ]]>``status=<![CDATA[ ]]>3<![CDATA[ ]]>``name=<![CDATA[ ]]>TestProfileFromExternApp<``[CDATA[ ]]> mask=<![CDATA[ `<snip..you get the idea>I just can't win! :)

Aaron B. 2010-01-26 15:43:34

I meant the whole string - not just around the quotes - but either way as I suspected, it's still formatting out the characters.In which case you could try using the CDataWrapper class from the other example I linked to, which implements IXmlSerializable explicitly so that it sends a string out as CDATA - by doing this you prevent all of the default WCF message formatting for that parameter's data - it's just that it needs to reach the WCF formatter as the CDataWrapper class, not a string - hence the need to alter the proxy code that has been generated for you.

Andras Zoltan 2010-01-26 15:51:25

Mmm...now that looks *exactly* like what I need. I'll give it a try...

Aaron B. 2010-01-26 16:10:14

Tried changing all the references to string xmlData to CDataWrapper and it looked like it was going to go, but then:{"There was an error reflecting 'xmlData'."}"The type tzGui.CDataWrapper may not be serialized with SOAP-encoded messages. Set the Use for your message to Literal."I changed the use=encoded to use=literal in the Campaign.WSDL (like so):***<wsdl:input><soap:body use="literal" namespace="http://tempuri.org/message/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" parts="sharedSecret xmlData" /></wsdl:input> *** Same error. Maybe I didn't change it in the correct spot?

Aaron B. 2010-01-26 17:35:56

I think you did - unless the WSDL should have been changed to reflect the fact that CDataWrapper type is now expected for that parameter instead of string.The question is, is it a facet of how the string itself is being serialized, or is it the message formatter through which this data is writing - if it's the latter, then we could swap types around however much we want, but it would still do the damned escaping, or non-escaping, depending upon which way you look at it ;). I'll try and lab up a service and client when I get a chance to see if I can reproduce and help further.

Andras Zoltan 2010-01-27 10:36:39

Answer 2

+1 A:

If I understand your long post, you seem to be building parts of your XML by using strings. Don't do that. Always use one of the XML APIs to create XML. It knows the quoting rules.

John Saunders 2010-01-30 00:52:34

Answer 3

A:

I never did fully figure out how to get this to work. However, I did find a solution. An ugly, hackish solution that I'm not proud of. But it worked.

In the interest of posterity, here's what I finally did. For each of the (10ish) calls I needed to make, I simply captured the SOAP call via fiddler, and then wrote a quick search-n-replace routine

    public string Newrule(string ruleName, DecisionSet decisionSet)
    {
        var soapString = "<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"no\"?><SOAP-ENV:Envelope " +
                         "xmlns:SOAPSDK1=\"http://www.w3.org/2001/XMLSchema\" xmlns:SOAPSDK2=\"http://www.w3.org/2001/XMLSchema-instance\" " +
                         "xmlns:SOAPSDK3=\"http://schemas.xmlsoap.org/soap/encoding/\" xmlns:SOAP-ENV=\"http://schemas.xmlsoap.org/soap/envelope/\"&gt;" +
                         "<SOAP-ENV:Body><SOAPSDK4:SetCondition xmlns:SOAPSDK4=\"http://tempuri.org/message/\"&gt;&lt;sharedSecret&gt;&lt;/sharedSecret&gt;" +
                         "<xmlData>&lt;SEARCHINFO_LIST&gt;&lt;SEARCH_INFO action=&quot;add&quot; status=&quot;3&quot; " +
                         "name=&quot;" + ruleName + "&quot; mask=&quot;0&quot; DecisionSet_id=&quot;" + decisionSet.Id +
                         "&quot; DecisionSet_protected=&quot;N&quot; " +
                         "condition_protected=&quot;N&quot;&gt;&lt;CONDITIONS/&gt;&lt;EXPRESSIONS/&gt;&lt;/SEARCH_INFO&gt;&lt;/SEARCHINFO_LIST&gt;" +
                         "</xmlData></SOAPSDK4:SetCondition></SOAP-ENV:Body></SOAP-ENV:Envelope>";

        var headerUrl = "http://tempuri.org/action/DecisionSet.SetCondition";
        var serviceUrl = "/webservice/DecisionSet.WSDL";
        var result = sender.MakeRequest(soapString, serviceUrl, headerUrl,null);
        var idSearch = @"SEARCH_INFO id=&quot;(\d+)&quot;";

        var ruleId = Regex.Match(result, idSearch).Groups[1].Value;

        return ruleId;
    }

This called a simple routine to make an http call with the appropriate headers. Inelegant, but it worked.

    public string MakeRequest(string requestString, string serviceUrl, string headerUrl, string useragent)
    {
        string query = requestString.Replace(@"<sharedSecret></sharedSecret>", "<sharedSecret>"+secret+"</sharedSecret>");
        query = query.Replace(@"<SessionID></SessionID>", "<SessionID>" + secret + "</SessionID>");
        HttpWebRequest req = (HttpWebRequest)WebRequest.Create(server + serviceUrl);
        //if (proxy != null) req.Proxy = new WebProxy(proxy, true);
        req.Headers.Add("SOAPAction", headerUrl);
        if (useragent == null)
            req.UserAgent = "SOAP Toolkit 3.0";
        else
        {
            req.UserAgent = useragent;
        }
        req.ContentType = "text/xml;charset=\"utf-8\"";
        req.Accept = "text/xml";
        req.Method = "POST";
        Stream stm = req.GetRequestStream();

        StreamWriter sw = new StreamWriter(stm);
        sw.Write(query);
        sw.Flush();
        stm.Close();
        WebResponse resp = req.GetResponse();
        stm = resp.GetResponseStream();
        StreamReader r = new StreamReader(stm);
        string response = (r.ReadToEnd());

        return response;
    }

Aaron B. 2010-02-09 18:50:14

ansaurus

tags:

views:

answers:

Getting quotes in innerXML to go on the wire as "

related questions

ansaurus

tags:

views:

answers:

Getting quotes in innerXML to go on the wire as &quot;

related questions

Getting quotes in innerXML to go on the wire as "