cancel
Showing results for 
Search instead for 
Did you mean: 

With the latest upgrade of ready API to 1.8.0, my previous xpaths do not work.

Highlighted
New Contributor

With the latest upgrade of ready API to 1.8.0, my previous xpaths do not work.

I was using the XML response of a JDBC request  as an input to another rest step using the 'Get data' option 

 

Previously it used to create an xpath like  ( '${Get some value#ResponseAsXml#//Results[1]/ResultSet[1]/Row[5]/COLUMN_ONE[1]}' )" (in version 1.7.0)

 

But now, it doesn't work.

If I change the casing of COLUMN_ONE to column_one in above xpath, it starts working otherwise it throws an error

{"message":"Unexpected character (',' (code 44)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')\n at [Source: java.io.ByteArrayInputStream@54bd3f5b; line: 2, column: 19]"}

 

 Please suggest a workaround, as i have lots of JDBC requests in my project and changing the letter cases in all xpath requests would be a huge pain.

5 REPLIES 5
Highlighted
Moderator

Re: With the latest upgrade of ready API to 1.8.0, my previous xpaths do not work.

Hello,

 

There was a change in Ready API 1.7 maintenance and 1.8 to convert the column names to be the same casing as the table names for the JDBC request test step.  There is a defect open of SOAP-5974 to have option to have column names returned as UPPER CASE to keep the functionality working as previous for those that need it.  Will let you know when that defect is fixed.

 

 

Regards,

Marcus

SmartBear Support



Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
Highlighted
Community Manager

Re: With the latest upgrade of ready API to 1.8.0, my previous xpaths do not work.

 

Hi Ankursharma,

 

 

Also, please take a look at the following explanation posted by our Ready! API developer:

https://community.smartbear.com/t5/SoapUI-NG/XPath-Expression-to-RawRequests-doesn-t-work-after-upda...

---------
Tanya Gorbunova
SmartBear Community Manager

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
Highlighted
New Contributor

Re: With the latest upgrade of ready API to 1.8.0, my previous xpaths do not work.

Thank you for quick response Marcus. Would really appreciate if this gets fixed sooner.

Highlighted
New Contributor

Re: With the latest upgrade of ready API to 1.8.0, my previous xpaths do not work.

Hi Tanya,

 

I've gone through the write-up before i posted my question. I actually wanted something more specific to my problem so thought of creating a different thread.

But thanks for directing me to it. I appreciate your concern. 🙂

 

Thanks!

Highlighted
Moderator

Re: With the latest upgrade of ready API to 1.8.0, my previous xpaths do not work.

FYI, defect SOAP-5974 is fixed in the Ready API 1.8 maintenance build.  You can download the maintenance build using the below link.

 

https://support.smartbear.com/downloads/readyapi/nightly-builds/

 

Regards,

Marcus

SmartBear Support



Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
New Here?
Join us and watch the welcome video:
Announcements
Top Kudoed Authors