Contributions
Re: [Resolved] Environment Handling - Env to JDBC
I think the support was trying to say is just create one JDBC Connection. Create as many environments as you want. Now in the environment tab, select the environment you want to configure, select the single JDBC connection, click "Configures the selection data connection". Now you are configuring the DB connection for the environment you selected. After you are done with that connection, select other environment, and repeat the JDBC configuration process. After you all done, if you select different environment, you shall see the JDBC configurations will be different from environment to environment even you have only one line of JDBC connection (the values, like driver and connections string, for that connection will change from environment to environment). HTH.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.6KViews0likes0Comments[Escalated] Schema compliance assertion
Hi, I created a schema compliance assertion and it didn't work as I expected. I attached an archive file with 3 related files for your review. One is the response (response.xml). The other 2 are .wadl and .xsd files respectively. My schema compliance assertion was pointed to the .wadl file. As you can see from the response, it's missing a "listings" node. However, there is a listings node in the .xsd file. When I run the request, the assertion comes up as Valid, which is a surprise to me becuase clearly the response is missing a node. Did I miss anything?11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.7KViews0likes1Comment