ContributionsMost RecentMost LikesSolutionsRe: When did you change the JSON Path Expression format for 'add assertion for content' and why Both syntaxes are accepted. We changed the way it was generated to the latter in order to deal with the case of keys starting with a dot. (For example $['teachers'][0]['.hours']) The change was done in 1.9.0. Re: HTTP HEAD Request Could you supply a small project where you can reproduce this behavior? This doesn't happen to me when I tried it out. Re: SoapUI Maven Plugin v5.2.2 Hi, 5.2.2 is not released yet and therefore hasn't been uploaded to our maven repository. The latest release is 5.2.1. The latest version in our GitHub repository is 5.2.2-SNAPSHOT and that is the version used while developing 5.2.2. So go with 5.2.1 and you will have the latest released version of SoapUI. If you are really eager to try out the latest and greatest you can use 5.2.2-SNAPSHOT, but then you will have to build it yourself first. Re: Maven Soapui Plugin with json assertions does not work well in junit test Yes, SoapUI Pro licenses works for Ready! API 1.8 as well. Re: In Ready! API, DataSource Options, how can I use the "Start Row:" and "End Row:" ... Enter the row you want to start with in Start Row and the last row in End Row. Remember that these row are indexed from zero, so for your example you would enter Start Row 12 and End Row 43. Re: REST requests erroring out Could you please a Ready! API project where this error occurs? That would make it possible for us to test out what could be wrong. Re: How to Automaticly Start a JMS Virt in SOAP UI NG with ServiceV Pro A maintenance build in which virtrunner commandline can run JMS virts is now available from https://support.smartbear.com/downloads/readyapi/nightly-builds/ Re: How to Automaticly Start a JMS Virt in SOAP UI NG with ServiceV Pro Oops, we will fix so that JMS Virts will work from the virtrunner commandline. I'll let you know when the maintenance build is available. Regarding the error message in the testrunner. I also get those in the log, but the JMS Virt actually starts fine for me. The error comes from the Hermes Library, which is used to connect to JMS engines, but I don't really know why it logs those errors. Re: SoapUI Pro vs Ready!API maven plugin Yes, there won't be any more updates to soapui-pro-maven-plugin. Re: SoapUI Pro vs Ready!API maven plugin Hi! I recommend you to use the Ready! API maven plugin. When you use that it is Ready! API that is run in the background. If you were to use the old SoapUI Pro maven plugin features introduced in Ready! API wouldn't work.