Question
Pega Problems with Quotation marks?("<" changing to "&lt;")
Hi everybody,
i am building a SOAP connect and right now i have a strange behaviour during this connect!
Within the SOAP Connect named "sendData" I have created a request (XML Stream) and a Response (XML ParseRule) part. The structure of the XML Stream Looks like that:
<Pic start------------------------------------------------------------------------------->
<Pic end------------------------------------------------------------------------------->
that is corresponding to the XML structure i got:
<Pic start------------------------------------------------------------------------------->
<soapenv:Envelope xmlns:soapenv="http://......." xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body><ns1:insert xmlns:ns1=http://insert........>
<ns1:pBean>
<ns1:serviceId>NBAInbound</ns1:serviceId>
<ns1:xml><![CDATA[<?xml version="1.0" encoding="ISO-8859-1"?>
<vtwta>
<-- some kind of Data -->
</vtwta>]]>
</ns1:xml>
</ns1:pBean>
</ns1:insert>
</soapenv:Body>
</soapenv:Envelope>
<Pic end------------------------------------------------------------------------------->
The property .XMLRequest will have the whole string part of <ns1:xml>! The property will be filled by a data transform, which Looks like that:
<Pic start------------------------------------------------------------------------------->
<Pic End------------------------------------------------------------------------------->
So everthing wihtin the <ns1:xml> is a string, starting with <
<Pic end------------------------------------------------------------------------------->
I cannot find a plausible solution, anybody who could help me?
Thanks a lot
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
On thing to check for is the use of cross site scripting filters. They can replace potentially dangerous characters like < with their url encodings like <.
Hi Kevin,
PRPC is 7.1.7 and here is copy/paste the relevant entry from the pega log file:
2015-11-10 10:21:52,997 [ WebContainer : 11] [TABTHREAD4] [ IACService:01.01.01] ( httpclient.wire.content) DEBUG sl007312.dcm.allianz|naimucby.wwg00m.rootdom.net|Rule-Connect-SOAP.AzD-IACService-Work-IACService.SendData MYNAME@COMPANY - >> "<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:insert xmlns:ns1="http://insert.vtw.micws.company.com"> <ns1:pBean> <ns1:serviceId>NBAInbound</ns1:serviceId> <ns1:xml><![CDATA[<?xml version="1.0" encoding="ISO-8859-1"?><vtwta><processtype>EBiz Standard</processtype><session><serviceid>NBAInbound</serviceid><product>NBA INBOUND_8 Info PK</product><businesscase>Hapftpflichtversicherung</businesscase></session><partner><type>PK</type><salutation>Frau</salutation><name>Fisch</name><firstname>Franz</firstname><street>Dessauerstra[0xc3][0x9f]e</street><streetnr>1</streetnr><zipcode>98272</zipcode><city>Passau</city><birthdate>31.12.1984</birthdate></partner><agency><vtgid>405130999</vtgid></agency><properties></properties><message>Das ist ein neuer Test 100[0xe2][0x82][0xac] - PEGA</message></vtwta>]]></ns1:xml> </ns1:pBean> </ns1:insert></soapenv:Body></soapenv:Envelope>"
As you can see the Problem occurs only within the CDATA String in <ns1:xml> I guess Pega cannot handle this right for SOAP!
For example if i have a look in the clipboard the XML string looks right but this is only a UI error i guess.
Thanks in advance
Accepted Solution
Hi Norman,
Please refer to this SA: https://pdn.pega.com/support-articles/characters-improperly-encoded-in-the-same-xml-streams
Appears to be the same issue with root cause analysis and options, one of them involves change on the service side, unfortunately.
Hi Norman,
In XML stream rule, try changing the mode to literal for the tag for which < is getting replaced with <. It should work.
Can you specify your PRPC version and capture the actual complete soap request to your web service provider? If possible, the error inside Pega logs (attach the whole file is better).