cancel
Showing results for 
Search instead for 
Did you mean: 

ReadyAPI 3.1.0 - Property Transfer with xQuery throws issue

SOLVED
Highlighted
New Contributor

ReadyAPI 3.1.0 - Property Transfer with xQuery throws issue

With the latest update to ReadyAPI 3.1.0, I am getting issues on property transfer steps that used the XQuery path language.

[java.lang.NoSuchMethodException: org.apache.xmlbeans.impl.xquery.saxon.XBeansXQuery.(java.lang.String,java.lang.String,java.lang.Integer,org.apache.xmlbeans.XmlOptions)]

This appears to be due to the change in the jar files. (removing xbean_xpath-2.4.0.jar and using xmlbeans-xpath-2.6.0.jar) 


Is there a way to continue using the XQuery with this release or are we being forced to now use XPath only?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Moderator

Re: ReadyAPI 3.1.0 - Property Transfer with xQuery throws issue

@NickMitricka ,

 

Thank you for providing the details, but, I cannot reproduce the issue anyway. I recommend that you create a new case here: https://support.smartbear.com/message/?prod=ReadyAPI and provide your project file.


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

View solution in original post

4 REPLIES 4
Community Hero

Re: ReadyAPI 3.1.0 - Property Transfer with xQuery throws issue

May be it would be good to open a support case to get a quicker response.


Regards,
Rao.
Highlighted
Moderator

Re: ReadyAPI 3.1.0 - Property Transfer with xQuery throws issue

Hi @NickMitricka,

 

It seems that the issue depends on the XQuery that you use. I've tried with the sample project on my side and the Property Transfer test step works fine for me.

 

Can you provide a screenshot of the Property Transfer test step settings and the XML content so that I could try to reproduce the issue?


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

Re: ReadyAPI 3.1.0 - Property Transfer with xQuery throws issue

@Nastya_Khovrina 
To give a little background, as I'm not sure that the screen shot will provide significant value.  We have a login page (html) that I am scraping to pull a URL that is needed for submitting a form.  The expression we are using is

//form[1]/@action

(technically more of an XPath expression); however, this worked in prior versions.

 

Screen Shot 2020-02-20 at 10.45.13 AM.png

A slightly different example that I'm seeing within assertions. We are making a call to an API and getting back data such as:

<Response xmlns="[REDACTED]">
   <phoneNumbers>
      <e>
         <display>555555555</display>
         <type>work</type>
         <value>5555555</value>
         <primary>true</primary>
      </e>
      <e>
         <display>123-555-9999</display>
         <type>mobile</type>
         <value>123-555-9999</value>
      </e>
   </phoneNumbers>
</Response>

Within this API the values can come back in either order, so we use xQuery assertion to check it:

The XQuery Match assertion failed for the following path: [declare namespace ns1='[REDACTED]';

<Response>
	{

	for $x in //ns1:phoneNumbers/ns1:e/ns1:type/text()
                        where $x='${#TestSuite#phoneNumberTypeWork}'
                        return  data($x)

	}
</Response>]. Class name: RuntimeException; Error Message: java.lang.NoSuchMethodException: org.apache.xmlbeans.impl.xquery.saxon.XBeansXQuery.<init>(java.lang.String,java.lang.String,java.lang.Integer,org.apache.xmlbeans.XmlOptions).

 

Highlighted
Moderator

Re: ReadyAPI 3.1.0 - Property Transfer with xQuery throws issue

@NickMitricka ,

 

Thank you for providing the details, but, I cannot reproduce the issue anyway. I recommend that you create a new case here: https://support.smartbear.com/message/?prod=ReadyAPI and provide your project file.


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

View solution in original post

New Here?
Join us and watch the welcome video:
Top Kudoed Authors