SoapUI3.0.1 (not the Plug-in) within Maven - updated..
Hi all,
I'm building a suite of tests round a (Grails) tool designed as to simulate a web service. I'm using SoapUI3.0.1 to validate the SOAP the app generates against the WSDL of the web service the app is mocking.
The tests (inc my SoapUI based WSDL test) run fine from the command line, as long as the SoapUI3.0.1 jar and all its dependent jars are placed in the app's /lib dir.
My aim is to Mavenise this app, and ultimately add it to our TeamCity CI setup. I have almost completed this task. The only remaining sticking point is my SoapUI based test.
I'm using the Grails Selenium RC plug-in elsewhere in the test suite, and I've build my SopaUI test as a Selenium RC, as this ensures that Maven starts the application server before running the tests, ensuring my test has the dummy WS endpoint available for it to call.
My problem is that when I call the mvn integration-test target, Maven runs through and fails on the SoapUI test (i.e. at the point the test is run), claiming it can't find a class that lives in the SoapUI jar file. It seems to be compiling the test class at runtime and the groovyc compiler is throwing a bunch of 'unable to resolve class' compiler errors. I've of course included the jar as a dependency in the pom:
...
eviware
soapui
3.0.1
test
...
Update:
Somehow my build is now acknowledging the existance of the soapui 3.0.1 jar file - the compiler errors that its lack was causing have evaporated. However, I'm still not there yet. I'm now getting a TypeNotPresentException looking for 'com.eviware.soapui.config.AbstractRequestConfig'. I've found this particular class in soapui-xmlbeans-3.0.1.jar, which I've added to the pom, but to no avail.
So, I've got both dependencies in the pom. If I remove both.. I get back to the original position of the class not found exceptions compiling my test class. If I add the soapui 3.0.1 jar, these go away to be replaced with the exception missing AbstractRequestConfig. If I add in the dependency to the pom for the jar that contains this class...no joy. It looks as if Maven is picking up some dependencies but not others.
So...has anyone else taken this route to using SoapUI with Maven and been able to resolve all the various dependencies? Any pointers?
TIA
Paul
I'm building a suite of tests round a (Grails) tool designed as to simulate a web service. I'm using SoapUI3.0.1 to validate the SOAP the app generates against the WSDL of the web service the app is mocking.
The tests (inc my SoapUI based WSDL test) run fine from the command line, as long as the SoapUI3.0.1 jar and all its dependent jars are placed in the app's /lib dir.
My aim is to Mavenise this app, and ultimately add it to our TeamCity CI setup. I have almost completed this task. The only remaining sticking point is my SoapUI based test.
I'm using the Grails Selenium RC plug-in elsewhere in the test suite, and I've build my SopaUI test as a Selenium RC, as this ensures that Maven starts the application server before running the tests, ensuring my test has the dummy WS endpoint available for it to call.
My problem is that when I call the mvn integration-test target, Maven runs through and fails on the SoapUI test (i.e. at the point the test is run), claiming it can't find a class that lives in the SoapUI jar file. It seems to be compiling the test class at runtime and the groovyc compiler is throwing a bunch of 'unable to resolve class' compiler errors. I've of course included the jar as a dependency in the pom:
...
...
Update:
Somehow my build is now acknowledging the existance of the soapui 3.0.1 jar file - the compiler errors that its lack was causing have evaporated. However, I'm still not there yet. I'm now getting a TypeNotPresentException looking for 'com.eviware.soapui.config.AbstractRequestConfig'. I've found this particular class in soapui-xmlbeans-3.0.1.jar, which I've added to the pom, but to no avail.
So, I've got both dependencies in the pom. If I remove both.. I get back to the original position of the class not found exceptions compiling my test class. If I add the soapui 3.0.1 jar, these go away to be replaced with the exception missing AbstractRequestConfig. If I add in the dependency to the pom for the jar that contains this class...no joy. It looks as if Maven is picking up some dependencies but not others.
So...has anyone else taken this route to using SoapUI with Maven and been able to resolve all the various dependencies? Any pointers?
TIA
Paul