nicorette
15 years agoOccasional Contributor
JDBC Request - X-Path Match leads to NullPointerException
Hello,
i am using a JDBC-Request on a SQL-Database with a few X-Path assertions. My SQL-Query is something like this "Select * FROM TABLE WHERE".
I am getting (as expected) two "Row"-Elements in the "ResultSet". I check the whole structure of each Row-Structure-Element with an XPath-Assertions:
First X-Path-Expression:
//Row[1]
Second X-Path-Expression.
//Row[2]
However, i am always getting the following error-message for the second X-Path-Assertion:
Curiously, the assertion for the first Row-Element does not produce any exceptions and works as expected.
Using //Row[@rowNumber='2'] instead leads to the same problem. If you check an element directly like this "//Row[2]/child" there is no problem.
The problem can be reproduced with Soap-UI-Pro, Nightly-Builds, etc.
i am using a JDBC-Request on a SQL-Database with a few X-Path assertions. My SQL-Query is something like this "Select * FROM TABLE WHERE".
I am getting (as expected) two "Row"-Elements in the "ResultSet". I check the whole structure of each Row-Structure-Element with an XPath-Assertions:
First X-Path-Expression:
//Row[1]
Second X-Path-Expression.
//Row[2]
However, i am always getting the following error-message for the second X-Path-Assertion:
Curiously, the assertion for the first Row-Element does not produce any exceptions and works as expected.
Using //Row[@rowNumber='2'] instead leads to the same problem. If you check an element directly like this "//Row[2]/child" there is no problem.
The problem can be reproduced with Soap-UI-Pro, Nightly-Builds, etc.