Forum Discussion

psi108's avatar
psi108
New Contributor
16 years ago

soapui changes response? CDATA?

hello,

go a strange problem.

this is how the raw response looks:
TTP/1.1 200 OK
Server: nginx/0.6.32
Date: Sun, 22 Feb 2009 22:20:58 GMT
Content-Type: text/xml; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
X-Powered-By: PHP/5.2.8-0.dotdeb.1
Set-Cookie: symfony=935e91c33045e5b99c6b70e7d6e97ae9; path=/
Set-Cookie: symfony=8e1d73e234a444ac1a0738a92b642677; path=/



e24cf2727a0582446a1b857eb62b86c8

 
 
 



So - this is how the response is shown in the XML Tab:
<?xml version="1.0" encoding="utf-8"?><br /><result action="session.signon" api="1.0" status="0"><br /><api_key>e24cf2727a0582446a1b857eb62b86c8</api_key><br /><country_code>0+49</country_code><br /><products_allowed><br />&nbsp; <product id="1" name="Einer zahlt" payment="group" /><br />&nbsp; <product id="2" name="Empf&auml;nger zahlt" payment="receiver" /><br />&nbsp; <product id="3" name="Sender zahlt" payment="sender" /><br /></products_allowed><br /></result>

wtf? :-)
is this as it should be, or a bug?

using soap ui 2.5.1 pro

thx for your help!

14 Replies

Sort By
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    16 years ago
    Hi Christian,

    actually, it's a bit in-between.. the xml contains an undefined entity (ä), which makes soapUI believe that this is not valid xml and thus wraps it in a CDATA block. I'll try to improve this somehow, will be in the upcoming nightly build..

    regards!

    /Ole
    eviware.com
  • psi108's avatar
    psi108
    New Contributor
    16 years ago
    hello,

    my soapui pro licence starts to get useless with this bug....

    any news?
  • NiclasReimertz's avatar
    NiclasReimertz
    Staff
    16 years ago
    Hi,

    The issue is a moral dilemma.

    being a developer, not a tester, Ole expressed himself delicately. Being more test oriented, I'll be a bit rougher: It is not a bug in soapUI. You are not allowed have have undefined entities in attributes. Period.

    As a tester, I would take this to the developers as a bug in the implementation and make sure it gets fixed, any standards based consumer will not accept the response. This mights change if the only consumers are internal only where you can allow for them to consume the response even though it is faulty.

    Our dilemma is:
    soapUI is a Testing Tool that should note errors. If we allow undefined entities, and you publish the the web service, you might have customers screaming "WebSphere says the XML is malformed" or "JBoss says this is faulty", in which case we would be doing you a disservice by allowing it.

    So our internal discussion is, "What to do? What is correct tool behavior?". What we know is, we can't allow this straight of the bat but there might be useful to cover this, where you would like to allows certain faulty behaviors in the web services, the only question is how to make it useful, general  and usable.

    I'm terribly sorry you have to wait, but we want to make sure this is handled right in soapUI.

    Meanwhile I'd really like to recommend you to talk to the people who built the web service. You never know how it is going to be consumes, there might be problems when trying to consume it in a new client (by for example a mobile app) or if it is used on multiple platforms.

    For example, save


    e24cf2727a0582446a1b857eb62b86c8

     
     
     




    as an XML file and try opening it in Firefox, Chrome or Internet Explorer. They will all complain

    the correct xml should be



    e24cf2727a0582446a1b857eb62b86c8

     
     
     



    Best Regards
    niclas
    eviware.com
  • Joao_Mendes's avatar
    Joao_Mendes
    Occasional Contributor
    15 years ago
    Hi,
    I'm having a similar problem. I have a SOAP service that returns:

    <?xml version="1.0" encoding="utf-8"?><resposta xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><dadosPed></dadosResp></resposta>


    soapui is inserting a CDATA tag after the is this correct??
    I think you do this because it interprets the
    Example:


     
         
            <?xml version="1.0" encoding="utf-8"?><resposta xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><dadosPed><idReport>0916</idReport><idOrig>0916</idOrig><devId><nifNipc>123456</nifNipc></devId><atrz>true</atrz></dadosPed><dadosResp><dtRep>2009-04-30</dtRep><numPart>16</numPart><prestMes>1046</prestMes><nm><![CDATA[JOHN DOE]]></nm><infSldAgd><vaAgd>298</vaAgd><nvResp>002</nvResp><sitCred><sit>002</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>011</prodFin><vaAgd>1494</vaAgd><nvResp>002</nvResp><sitCred><sit>001</sit></sitCred><przOrig>005</przOrig><przResi>005</przResi><prodFin>011</prodFin><vaAgd>11890</vaAgd><nvResp>001</nvResp><sitCred><sit>001</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>002</prodFin><vaAgd>8246</vaAgd><nvResp>002</nvResp><sitCred><sit>001</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>009</prodFin><vaAgd>1625</vaAgd><nvResp>002</nvResp><sitCred><sit>002</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>009</prodFin><vaAgd>4494</vaAgd><nvResp>002</nvResp><sitCred><sit>001</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>002</prodFin><vaAgd>150</vaAgd><nvResp>002</nvResp><sitCred><sit>002</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>002</prodFin><vaAgd>53616</vaAgd><nvResp>005</nvResp><sitCred><sit>002</sit></sitCred><przOrig>009</przOrig><przResi>009</przResi><prodFin>010</prodFin><gar><tipo>001</tipo><val>108448</val></gar><vaAgd>13051</vaAgd><nvResp>002</nvResp><sitCred><sit>001</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>011</prodFin><vaAgd>996</vaAgd><nvResp>001</nvResp><sitCred><sit>002</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>009</prodFin><vaAgd>465</vaAgd><nvResp>002</nvResp><sitCred><sit>001</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>003</prodFin><vaAgd>15930</vaAgd><nvResp>001</nvResp><sitCred><sit>001</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>009</prodFin><vaAgd>6930</vaAgd><nvResp>002</nvResp><sitCred><sit>001</sit></sitCred><przOrig>006</przOrig><przResi>006</przResi><prodFin>011</prodFin><vaAgd>7777</vaAgd><nvResp>001</nvResp><sitCred><sit>001</sit></sitCred><przOrig>006</przOrig><przResi>005</przResi><prodFin>011</prodFin><vaAgd>423</vaAgd><nvResp>001</nvResp><sitCred><sit>001</sit></sitCred><przOrig>005</przOrig><przResi>003</przResi><prodFin>011</prodFin></infSldAgd></dadosResp></resposta>
         
     


    As you can see after "John Doe" there are 4 ].

    Thanks
    João Mendes
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    15 years ago
    Hi,

    this actually might be ok, it looks as if the reposta element contained an XML string that itself contained a CDATA section; soapUI creates this construct to wrap it; it isn't against any rules but a bit confusing.. anyhow.. can you show the http-log containing this response so we can see what it looks like before soapUI starts processing it?

    regards!

    /Ole
    eviware.com
  • Joao_Mendes's avatar
    Joao_Mendes
    Occasional Contributor
    15 years ago
    Hio,
    Here it is

    Thu Jun 18 16:39:11 BST 2009:DEBUG:<< "<?xml version="1.0" encoding="utf-8"?><resposta xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><dadosPed><idReport>0916</idReport><idOrig>0916</idOrig><devId><nifNipc>123456</nifNipc></devId><atrz>true</atrz></dadosPed><dadosResp><dtRep>2009-04-30</dtRep><numPart>16</numPart><prestMes>1046</prestMes><nm><![CDATA[JOHN DOE]]></nm><infSldAgd><vaAgd>298</vaAgd><nvResp>002</nvResp><sitCred><sit>002</sit></sitCred><przOrig>001</przOrig><przResi>001<"
    Thu Jun 18 16:39:11 BST 2009:DEBUG:<< "/przResi><prodFin>011</prodFin><vaAgd>1494</vaAgd><nvResp>002</nvResp><sitCred><sit>001</sit></sitCred><przOrig>005</przOrig><przResi>005</przResi><prodFin>011</prodFin><vaAgd>11890</vaAgd><nvResp>001</nvResp><sitCred><sit>001</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>002</prodFin><vaAgd>8246</vaAgd><nvResp>002</nvResp><sitCred><sit>001</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>009</prodFin><vaAgd>1625</vaAgd><nvResp>002</nvResp><sitCred><sit>002</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>009</prodFin><vaAgd>4494</vaAgd><nvResp>002</nvResp>&l"
    Thu Jun 18 16:39:11 BST 2009:DEBUG:<< "t;sitCred><sit>001</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>002</prodFin><vaAgd>150</vaAgd><nvResp>002</nvResp><sitCred><sit>002</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>002</prodFin><vaAgd>53616</vaAgd><nvResp>005</nvResp><sitCred><sit>002</sit></sitCred><przOrig>009</przOrig><przResi>009</przResi><prodFin>010</prodFin><gar><tipo>001</tipo><val>108448</val></gar><vaAgd>13051</vaAgd><nvResp>002</nvResp><sitCred><sit>001</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>011</prodFin><vaAgd>996</vaAgd><nvResp>001</nvResp><sitCred><sit>002</"
    Thu Jun 18 16:39:11 BST 2009:DEBUG:<< "sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>009</prodFin><vaAgd>465</vaAgd><nvResp>002</nvResp><sitCred><sit>001</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>003</prodFin><vaAgd>15930</vaAgd><nvResp>001</nvResp><sitCred><sit>001</sit></sitCred><przOrig>001</przOrig><przResi>001</przResi><prodFin>009</prodFin><vaAgd>6930</vaAgd><nvResp>002</nvResp><sitCred><sit>001</sit></sitCred><przOrig>006</przOrig><przResi>006</przResi><prodFin>011</prodFin><vaAgd>7777</vaAgd><nvResp>001</nvResp><sitCred><sit>001</sit></sitCred><przOrig>006</przOrig><przResi>005</przResi><prodFin>011<"
    Thu Jun 18 16:39:11 BST 2009:DEBUG:<< ";/prodFin><vaAgd>423</vaAgd><nvResp>001</nvResp><sitCred><sit>001</sit></sitCred><przOrig>005</przOrig><przResi>003</przResi><prodFin>011</prodFin></infSldAgd></dadosResp></resposta>    "
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    15 years ago
    Hi,

    thanks! As I suspected (search for the string "![CDATA[JOHN DOE]]" in this); soapUI prefers CDATA sections over entities for longer XML strings (both are syntactically valid), which results in this construct.. actually its the first time I've seen this, I feel like a birdwatcher catching sight of a very rare bird :-)

    regards!

    /Ole
    eviware.com
  • Joao_Mendes's avatar
    Joao_Mendes
    Occasional Contributor
    15 years ago
    Ok,
    But why does soapui close the CDATA after the "John DOE" CDATA is closed?


    Thanks
    João Mendes