01 March 2010 - 3.5 |
The soapUI Nature allows integrated access to all soapUI functionality directly from within a Java project.
The following example walks through a "top down" scenario:
Start by creating an empty Java project and enabling the soapUI Nature from the projects popup menu:
If enabling goes will, you will see a "SoapUI Web Services" node in the project:
When shown in the Eclipse Project Explorer View, this node behaves like a standard soapUI project node. Its right-click menu includes a "soapUI" menu with available project actions:
You can either manually create a WSDL or WADL in your project (using for example the
formidable Web Tools Project WSDL Editor) or just import one into your project using one of the standard
"Add WSDL" or "Add WADL" actions. When creating the WSDL or WADL in your project, right-click on the file and select "soapUI -> Add to soapUI Project" Once imported, the WSDL or WADL is shown as a "standard" soapUI Interface node under the "soapUI Web Services" node: | ![]() |
Now its time to generate some code... select the "Generate -> Axis 1.X Artifacts" menu option from the Interface nodes popup menu which will show the below dialog
Select the desired options and set the output folder to a Java source folder in your project..
Select the "Generate" button which will invoke Axis (as configured under "Preferences -> soapUI -> Integrated Tools") and show the output in the console window:
The generated classes are now visible under the Java source node (refresh first!)
(The classes are marked red above since the axis-libraries are not in the projects classpath. These will be added automatically by soapUI in a future version)
After implementing and deploying your Web Service to the desired container, you can now start sending web service requests "as usual"... good luck!