Forum Discussion
Kathryn_O_Malle
14 years agoContributor
Hi,
After a break I'm able to update on what I've been able to achieve with this one. I've also attached a set of support files with error logs, etc to help out. I've determined the following points in trying to get LoadUI to run my SoapUI project.
From the above I think i have found the following integration issues (with the described workarounds):
Am I right in thinking that the above are "features" of the current LoadUI version? If yes do I need to cross-post them to the LoadUI bug forum for you?
Kind regards
Adam Hall
After a break I'm able to update on what I've been able to achieve with this one. I've also attached a set of support files with error logs, etc to help out. I've determined the following points in trying to get LoadUI to run my SoapUI project.
- 1) The SoapUI testcase is happy to run in standalone mode without any modifications
2) When I try and use LoadUI to execute the SoapUI testcase using a nightly build version of LoadUI I still encounter an error (please see error log "24Jan2011_LoadUI_Error_Log PRE ext folder creation")
3) When I add an "ext" folder directly beneath the LoadUI home directory and place into it the rt.jar file I get a different error (please see error log "16Feb2011_LoadUI_Error_Log JDBC connection NOT registered")
4) Only when I also add in an additional line of code to my SoapUI testcase to register the ODBC connection will the test case run successfully
// ** Extra line of code here...
com.eviware.soapui.support.GroovyUtils.registerJdbcDriver("sun.jdbc.odbc.JdbcOdbcDriver")
From the above I think i have found the following integration issues (with the described workarounds):
- a) The "/ext" folder is not automatically created during the LoadUI installation procedure
b) Any jar files required by the tools must be placed into the "ext" folder in (a)
c) As per the attached start up batch files, it does not appear that any supplied class path definitions are used right now (as the batch files used to start both LoadUI and SoapUI contain classpath definitions)
d) Each time an ODBC connection is used in a SoapUI groovy script step there must be an associated ODBC registration line of code (not required when running the SoapUI testcase in standalone mode)
Am I right in thinking that the above are "features" of the current LoadUI version? If yes do I need to cross-post them to the LoadUI bug forum for you?
Kind regards
Adam Hall