Forum Discussion

simonsen78's avatar
simonsen78
New Contributor
15 years ago

SoapUI 3.6.2 - JDBC returning XML minus underscores

Mjello

I tried downloading SoapUI PRO 3.6.2 to stop the Forms view messing up the XML madness But now I have an issue with all my JDBC steps returning the XML response, minus the underscores used in the database:


3.6 JDBC response (The correct one):
---------------------------------------
<Results>
<ResultSet fetchSize="10">
<Row rowNumber="1">
<MEANS_PAY_NO>2080</MEANS_PAY_NO>
<NAME_ID_NO>53791</NAME_ID_NO>
etc...

3.6.2 JDBC response:
-----------------------------
<Results>
<ResultSet fetchSize="10">
<Row rowNumber="1">
<MEANSPAYNO>2080</MEANSPAYNO>
<NAMEIDNO>53791</NAMEIDNO>
etc...

Is this something that there's an easy fix for?

5 Replies

  • mlenosgrande's avatar
    mlenosgrande
    Contributor
    15 years ago
    Ive met the same issue with jdbc test step.
    the quickest fix is to chnage your xpath and add or remove the undercores to match the result.
    Maybe you have 100 assertions. Edit them with NotePad++ or whateever and use the function search/replace in the xml project.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    15 years ago
    Hi!

    soapUI 3.6.2 normalizes the element names generated for the database columns to contain only characters, if you want I can add an exception for underscore character!?

    regards!

    /Ole
    eviware.com
  • simonsen78's avatar
    simonsen78
    New Contributor
    15 years ago
    soapUI 3.6.2 normalizes the element names generated for the database columns to contain only characters, if you want I can add an exception for underscore character!?

    I would love to get the underscore back!

    Otherwise I would have to change/check a ridiculous amount of testcases, assertions, property transfers, etc. And yes, Notepad++ could be a quick fix but I'm not sure what the reasoning behind normalizing the XML was in the first place...

    Would love not to have to spend time manually changing a 1000+ lines of XML, only to have it be 'fixed' in the next version of SoapUI.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    15 years ago
    Hi!

    ok, we could add an option for this (so you can turn it off). The reason was that queries with expressions like "select count(*) from.. " were resulting in invalid XML content

    regards!

    /Ole
    eviware.com
  • simonsen78's avatar
    simonsen78
    New Contributor
    15 years ago
    we could add an option for this (so you can turn it off)


    That would be great, thank you!