Apex Code Development You need to sign in to do that
Don't have an account?
Sankalp Jhingran Less than sign(<) is converting to <(HTML) in the SOAP request generated by SFDC
Hi All,
I have generated an apex class from a WSDL and I am making callouts to a third party webservice. It has a edit method which accepts 3 arguments, 1st username, 2nd password and 3rd accepts an XML within CDATA tags.
Callout is working fine when the request is generated using SOAP UI, however from salesforce all less than signs(<) in the 3rd parameter are getting converted to "<" in the final request.
Here is the line I am passing for the 3rd parameter in CDATA tag:
String xml = '<Contract id="Contract-6765031"><ContractName>1000 CRM Subscriptions2</ContractName><ContractId>2320</ContractId><Division>6749812</Division><SubDivision>6749934</SubDivision><Vendor>6749092</Vendor><Description>1000 CRM Subscriptions2</Description></Contract>';
XmlStreamWriter xsw = new XmlStreamWriter();
xsw.writeCData(xml);
String xmlString = xsw.getXmlString();
Here is the resulting string printed with CDATA tags:
00:04:24.047 (47225666)|USER_DEBUG|[73]|DEBUG|############## <![CDATA[<Contract id="Contract-6765031"><ContractName>1000 CRM Subscriptions2</ContractName><ContractId>2320</ContractId><Division>6749812</Division><SubDivision>6749934</SubDivision><Vendor>6749092</Vendor><Description>1000 CRM Subscriptions2</Description></Contract>]]>
Here is the debug for the request object:
00:16:20.067 (67571169)|USER_DEBUG|[312]|DEBUG|#######################1 edit_element:[apex_schema_type_info=(http://xmlns.enlighta.com/WebService, true, false), field_order_type_info=(in0, in1, in2), in0=sankalp@someemail.com, in0_type_info=(in0, http://xmlns.enlighta.com/WebService, null, 1, 1, false), in1=password, in1_type_info=(in1, http://xmlns.enlighta.com/WebService, null, 1, 1, false), in2=<![CDATA[<Contract id="Contract-6765031"><ContractName>1000 CRM Subscriptions2</ContractName><ContractId>2320</ContractId><Division>6749812</Division><SubDivision>6749934</SubDivision><Vendor>6749092</Vendor><Description>1000 CRM Subscriptions2</Description></Contract>]]>, in2_type_info=(in2, http://xmlns.enlighta.com/WebService, null, 1, 1, false)]
Now, when I saw the complete SOAP request in the debug log, I found < signs in the request for the 3rd parameter as below:
00:16:20.071 (71082584)|CALLOUT_REQUEST|[314]|<?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><env:Header /><env:Body><edit xmlns="http://xmlns.enlighta.com/WebService"><in0>sankalp@someemail.com</in0><in1>password</in1><in2><![CDATA[<Contract id="Contract-6765031"><ContractName>1000 CRM Subscriptions2</ContractName><ContractId>2320</ContractId><Division>6749812</Division><SubDivision>6749934</SubDivision><Vendor>6749092</Vendor><Description>1000 CRM Subscriptions2</Description></Contract>]]></in2></edit></env:Body></env:Envelope>
So, the xml reaching to the third party is incorrect.
Any help is appreciated.
Thanx,
Sankalp
I have generated an apex class from a WSDL and I am making callouts to a third party webservice. It has a edit method which accepts 3 arguments, 1st username, 2nd password and 3rd accepts an XML within CDATA tags.
Callout is working fine when the request is generated using SOAP UI, however from salesforce all less than signs(<) in the 3rd parameter are getting converted to "<" in the final request.
Here is the line I am passing for the 3rd parameter in CDATA tag:
String xml = '<Contract id="Contract-6765031"><ContractName>1000 CRM Subscriptions2</ContractName><ContractId>2320</ContractId><Division>6749812</Division><SubDivision>6749934</SubDivision><Vendor>6749092</Vendor><Description>1000 CRM Subscriptions2</Description></Contract>';
XmlStreamWriter xsw = new XmlStreamWriter();
xsw.writeCData(xml);
String xmlString = xsw.getXmlString();
Here is the resulting string printed with CDATA tags:
00:04:24.047 (47225666)|USER_DEBUG|[73]|DEBUG|############## <![CDATA[<Contract id="Contract-6765031"><ContractName>1000 CRM Subscriptions2</ContractName><ContractId>2320</ContractId><Division>6749812</Division><SubDivision>6749934</SubDivision><Vendor>6749092</Vendor><Description>1000 CRM Subscriptions2</Description></Contract>]]>
Here is the debug for the request object:
00:16:20.067 (67571169)|USER_DEBUG|[312]|DEBUG|#######################1 edit_element:[apex_schema_type_info=(http://xmlns.enlighta.com/WebService, true, false), field_order_type_info=(in0, in1, in2), in0=sankalp@someemail.com, in0_type_info=(in0, http://xmlns.enlighta.com/WebService, null, 1, 1, false), in1=password, in1_type_info=(in1, http://xmlns.enlighta.com/WebService, null, 1, 1, false), in2=<![CDATA[<Contract id="Contract-6765031"><ContractName>1000 CRM Subscriptions2</ContractName><ContractId>2320</ContractId><Division>6749812</Division><SubDivision>6749934</SubDivision><Vendor>6749092</Vendor><Description>1000 CRM Subscriptions2</Description></Contract>]]>, in2_type_info=(in2, http://xmlns.enlighta.com/WebService, null, 1, 1, false)]
Now, when I saw the complete SOAP request in the debug log, I found < signs in the request for the 3rd parameter as below:
00:16:20.071 (71082584)|CALLOUT_REQUEST|[314]|<?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><env:Header /><env:Body><edit xmlns="http://xmlns.enlighta.com/WebService"><in0>sankalp@someemail.com</in0><in1>password</in1><in2><![CDATA[<Contract id="Contract-6765031"><ContractName>1000 CRM Subscriptions2</ContractName><ContractId>2320</ContractId><Division>6749812</Division><SubDivision>6749934</SubDivision><Vendor>6749092</Vendor><Description>1000 CRM Subscriptions2</Description></Contract>]]></in2></edit></env:Body></env:Envelope>
So, the xml reaching to the third party is incorrect.
Any help is appreciated.
Thanx,
Sankalp
2.4 Character Data and Markup
Text consists of intermingled character data and markup. [Definition: Markup takes the form of start-tags, end-tags, empty-element tags, entity references, character references, comments, CDATA section delimiters, document type declarations, processing instructions, XML declarations, text declarations, and any white space that is at the top level of the document entity (that is, outside the document element and not inside any other markup).]
[Definition: All text that is not markup constitutes the character data of the document.]
The ampersand character (&) and the left angle bracket (<) must not appear in their literal form, except when used as markup delimiters, or within a comment, a processing instruction, or a CDATA section. If they are needed elsewhere, they must be escaped using either numeric character references or the strings " & " and " < " respectively. The right angle bracket (>) may be represented using the string " > ", and must, for compatibility, be escaped using either " > " or a character reference when it appears in the string " ]]> " in content, when that string is not marking the end of a CDATA section.
In the content of elements, character data is any string of characters which does not contain the start-delimiter of any markup and does not include the CDATA-section-close delimiter, " ]]> ". In a CDATA section, character data is any string of characters not including the CDATA-section-close delimiter, " ]]> ".
To allow attribute values to contain both single and double quotes, the apostrophe or single-quote character (') may be represented as " ' ", and the double-quote character (") as " " ".
Character Data
[14] CharData ::= [^<&]* - ([^<&]* ']]>' [^<&]*)
http://www.w3.org/TR/2008/REC-xml-20081126/#syntax
Also see the below threads about the Same
http://stackoverflow.com/questions/14345208/why-doesnt-lt-convert-to-while-gt-and-other-escape-characters-convert-app
http://www.soatothecloud.com/2011/07/how-to-convert-xml-to-soap-on-vordel.html
http://bytes.com/topic/net/answers/492941-replacing-lt-using-xslt
http://p2p.wrox.com/xml/49214-xml-tags-getting-converted-during-exchange.html
Regards,
Ashish