Contributions
Re: NullPointerException at com.eviware.soapui.impl.wsdl.teststeps.ProJdbcRequestTestStep
Himneiferbag, Yes. Seeing these exceptions for a long time and logging system getting filled with many such exceptions & makes it hard to troubleshoot other issues. I Tried followingworkaround suggested in another thread, but not much of help and issue still there. Workaround: in Ready! API 1.5. I’ve found a similar issue in our DB. Could you please check if the connection is set to "None" your test step? If it is, try the following workaround: Create a database connection in the "Databases" section and change connection from "None" to the database connection created in the JDBC test step. Result: I still see the expceptions7 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.7KViews0likes0CommentsRe: PostgresQL select query results giving tablename for each node in respose for ReadyAPI1.4.1
Thank you for the reply. My concern is with changing all the existing test steps (We had them in MS SQL and now migrating some envirnments to PostGreSQL). So it will be more work to build the logic and handle them separately. If ReadyAPI1.4.1 provides the similar response as SoapUI or other tools/drivers it should be good. I think its more of an issue/enhancement needed on ReadyAPI side.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.2KViews0likes0CommentsPostgresQL select query results giving tablename for each node in respose for ReadyAPI1.4.1
with ReadyAPI1.4.1 when did select query on PostGreSQL the response is having following format, <Results> <ResultSet fetchSize="0"> <Row rowNumber="1"> <TBLCNACCOUNTS.MASTER_USER_ID>1234</TBLCNACCOUNTS.MASTER_USER_ID> <TBLCNACCOUNTS.USER_NAME>abc</TBLCNACCOUNTS.USER_NAME> <TBLCNACCOUNTS.PASSWORD>pwd</TBLCNACCOUNTS.PASSWORD> </Row> </ResultSet> </Results> where as SoapUI Pro 5.1.2 gives the response for same scenario without tablename for each node as, <Results> <ResultSet fetchSize="128"> <Row rowNumber="1"> <MASTER_USER_ID>1234</MASTER_USER_ID> <USER_NAME>abc</USER_NAME> <PASSWORD>pwd</PASSWORD> </Row> </ResultSet> </Results> This is totally changing the formatting and re-use of properties from response to other test steps. Also, when switching from MS SQL DB to PostGreSQL (Migration Tests Or different environments have different DB servers), we see this as an issue with ReadyAPI1.4.1 Request you to review and eliminate table name in responses and keep same for all DB drivers. Thanks, DhanaRaj.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.3KViews0likes7Comments