Thanks for the update! I am making progress - slowly :-(
I encountered a class loader problem. I tried both: 1) adding the jar that contains my javabean to the SoapUI's bin/ext folder, and 2) using the com.eviware.soapui.support.ClasspathHacker.addURL( new URL("file://" + myjarpath) ) to load the jar.
I both cases I got the following exception triggered by the import statement:
Mon Jul 09 01:46:35 MDT 2012:ERROR:org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
Script2.groovy: 24: unable to resolve class com.abc.togw.services.lpql.clientsharedobjects.TogDto
@ line 24, column 1.
import com.abc.togw.services.lpql.clientsharedobjects.TogDto
^
org.codehaus.groovy.syntax.SyntaxException: unable to resolve class com.abc.togw.services.lpql.clientsharedobjects.TogDto
@ line 24, column 1.
at org.codehaus.groovy.ast.ClassCodeVisitorSupport.addError(ClassCodeVisitorSupport.java:148)
at org.codehaus.groovy.control.ResolveVisitor.visitClass(ResolveVisitor.java:1240)
at org.codehaus.groovy.control.ResolveVisitor.startResolving(ResolveVisitor.java:148)
I know that I am importing the proper class in the proper jar, as I am running on the side a stand alone small java program for verification and that works.
Is there a utility method for printing out the complete classpath that is in effect when the import statement is executed?
The SoapUI log has this log entry written when the script runs:
Mon Jul 09 02:17:35 MDT 2012:INFO:Added [file://C:/Documents and Settings/SoapUI/LpQ-1.0.6.jar] to classpath
Thanks,
Joseph H.
