Forum Discussion
SmartBear_Suppo
16 years agoSmartBear Alumni (Retired)
Hi Tom,
The procedure suggested by corki is the correct one.
After copying your JAR file(s) to $SOAPUI_HOME/bin/ext folder and restarting soapUI the public classes from the corresponding JAR file(s) should be visible to Groovy run-time after you import the corresponding symbols, i.e. Java types.
In Groovy, you can either import a Java type by either using FQN (i.e. fully-qualified name comprised out of package name and class name) or by using wild card notation (which allows you to import all types from a single package, excluding eventually sub packages).
Since I cannot find online the JAR you're referencing I cannot tell you what is the correct way to import GWTInvoker type. I suggest using JAR to find out what is the proper package name:
Then you should get the proper package name by removing slashes with dots.
Cheers!
/Nenad Nikolic a.k.a. Shonzilla
The procedure suggested by corki is the correct one.
After copying your JAR file(s) to $SOAPUI_HOME/bin/ext folder and restarting soapUI the public classes from the corresponding JAR file(s) should be visible to Groovy run-time after you import the corresponding symbols, i.e. Java types.
In Groovy, you can either import a Java type by either using FQN (i.e. fully-qualified name comprised out of package name and class name) or by using wild card notation (which allows you to import all types from a single package, excluding eventually sub packages).
Since I cannot find online the JAR you're referencing I cannot tell you what is the correct way to import GWTInvoker type. I suggest using JAR to find out what is the proper package name:
jar -tvf jeveragwutils.jar
Then you should get the proper package name by removing slashes with dots.
Cheers!
/Nenad Nikolic a.k.a. Shonzilla
Related Content
- 8 years ago
Recent Discussions
- 15 years ago