pcsoft.us.windevCopyright 2026, PC SOFT22 Aug 2016 22:26:00 Z18 Aug 2016 14:34:00 ZHi, I'm working on a SharePoint interface using the SP web services. This works pretty OK but I'm having a problem where the WX runtime tries to be too smart and breaks the XML being send. It's likely that I am missing something and that there is an XML standard to force data in an XML node NOT to be altered in any way by a parsing engine. I can't know it all of course... Anyway, here's the story: 1. The ISSUE: The WX runtime tries to be too intelligent and parses an XML body passed in a webservice parameter of string type into text without reserved xml characters. E.g. "< Query > becomes & ltQuery& gt… 2. The QUESTION: Is there a W-Language method/option or an XML attribute where we can force that the WX webservice execution engine does not parse xml text into text without reserved xml characters for a web service parameter of string type? [(<,>,&,…) becomes (& lt,& gt,& amp,…) etc.] As we need to pass an XML into a SharePoint parameter which is defined as a string parameter. 3. EXAMPLE: Sharepoint GetListItems Webservice SOAP 1.2 The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values. POST /_vti_bin/lists.asmx HTTP/1.1 Host: test.hamon.com Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> < soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope" > < soap12:Body > < GetListItems xmlns="http://schemas.microsoft.com/sharepoint/soap/" > < listName > string< /listName > < viewName > string< /viewName > < query > string< /query > < viewFields > string< /viewFields > < rowLimit > string< /rowLimit > < queryOptions > string< /queryOptions > < webID > string< /webID > < /GetListItems > < /soap12:Body > < /soap12:Envelope > Imported in WX as a web service... As you can see the Query parameter is defined as a string by the Sharepoint wsdl contract above but in practice it needs to be completed with an XML itself that contains the query in xml format. 4. Execution in WX (Simplified) This is how it looks in WX (simplified test block): ... //WS INIT Stuff //Set Web service address and authentication Lists..Address = pWSAddress Lists..Authentication = auNegotiate Lists..User = pWSUserName Lists..Password = pWSUserPassword Lists..MethodHTTP = httpPost Lists..IgnoreError = httpIgnoreExpiredCertificate+httpIgnoreInvalidCertificate+httpIgnoreInvalidCertificateName+httpIgnoreRedirection ... //DECLARE … SPLst is Lists.GetListItems SPWSResponse is Lists.GetListItemsResponse //SET PARAMS SPLst.listName = "AP" SPLst.query = [ < Query > < Where > < Eq > < FieldRef Name='ProjectID' / > < Value Type='Text' > a< /Value > < /Eq > < /Where > < /Query > ] SPWSResponse = Lists.GetListItems(SPLst) //Return Result IF ErrorOccurred() THEN ErrMsg:AddToList(pErrLst,soErrorMessage::EM_ERROR,"WEBSERVICE","Error encountered. Contact your supplier if the problem persists.",ErrorInfo(errMessage)) WXApplication::LogError(pErrLst) RESULT (False, WSResponse) ELSE RESULT (True, WSResponse) END 5. Response in WX returned by the Sharepoint server The following error was returned by the service by hErrorInfo(): Code: 'Server' Message: Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown. 6. Sharepoint server logs If we look on the server, we can trace the execution of the SOAP request which is broken at the point where the WX runtime replaced < by &lt: < ?xml version="1.0" encoding="UTF-8"?> < SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> < SOAP-ENV:Header/> < SOAP-ENV:Body> < ns1:GetListItems xmlns:ns1="http://schemas.microsoft.com/sharepoint/soap/" > < ns1:listName> AP< /ns1:listName > < ns1:query > &lt SOAP exception: System.Runtime.InteropServices.COMException (0x82000000): Element < Query > of parameter query is missing or invalid.… 7. And what if we use SOAPPrepare to get the XML to send manually? SOAPPrepare() works fine as well but does the exact same trick... This is the XML string returned by SOAPPrepare for the above WX code. As you can see the < Query > element is parsed as well by the WX Runtime Engine as non xml text... < ?xml version="1.0" encoding="UTF-8"? > < SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > < SOAP-ENV:Header/ > < SOAP-ENV:Body > < ns1:GetListItems xmlns:ns1="http://schemas.microsoft.com/sharepoint/soap/" > < ns1:listName > AP< /ns1:listName > < ns1:query > & lt;Query& gt;& #13; & lt;Where& gt;& #13; & lt;Eq& gt;& #13; & lt;FieldRef Name='ProjectID' /& gt;& #13; & lt;Value Type='Text'& gt;a& lt;/Value& gt;& #13; & lt;/Eq& gt;& #13; & lt;/Where& gt;& #13; & lt;/Query& gt; < /ns1:query > < /ns1:GetListItems > < /SOAP-ENV:Body > < /SOAP-ENV:Envelope > 8. CONCLUSION The WX runtime has altered the < Query > < Where >… string into non xml text & lt;Query& gt;& & lt;Where& gt; This is an unwanted behaviour. Therefore we would like to know if it is possible in W-Language or by a W3 XML standard to force the WX runtime not to alter an xml body if it passed intentionally into web service parameter of string type. TIA all for any feedback that leads to a solution ! Cheers, Peter Holemans ? PS: Never mind the extra spaces etc. in the XML files as I had to alter this in order for it to display reasonably within this forum software30WEBDEVen_UShttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter/read.awpmoderateur@pcsoft.fr (El moderador)webmaster@pcsoft.fr (El webmaster)guestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59175/read.awp22 Aug 2016 22:26:00 ZHi Bart, Thanks for the suggestion but I already tried that and the CDATA tag doesn't make any difference during the executio…https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59175/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59175/read.awpWX: Consume Web Service - String parameterguestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59174/read.awp22 Aug 2016 20:41:00 ZHi, Maybe you can insert a CDATA tag in where you can put your data that not should be interpreted as XML markup Regards, …https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59174/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59174/read.awpWX: Consume Web Service - String parameterguestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59172/read.awp22 Aug 2016 17:35:00 ZHi Peter, I hope you will find a nice solution. As for the delays, this is 24 to 48 hours of working hours. This means 3 t…https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59172/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59172/read.awpWX: Consume Web Service - String parameterguestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59169/read.awp22 Aug 2016 14:34:00 ZHi again Peter, Yep, in the help they say that the SOAP* commands can be used to “inject” some additional data in a soap quer…https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59169/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59169/read.awpWX: Consume Web Service - String parameterguestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59166/read.awp22 Aug 2016 14:28:00 ZHi Peter, So, if I understand, the Lists.GetListItems structure does not include the xml elements definition for the < query …https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59166/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59166/read.awpWX: Consume Web Service - String parameterguestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59165/read.awp22 Aug 2016 10:11:00 ZNobody?https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59165/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59148-consume-web-service-string-parameter-59165/read.awpWX: Consume Web Service - String parameter