15 January 2008 - 2.0.1 home user-guide eclipse intellij netbeans maven PDF files forums bugs sourceforge eviware.com






soapUI Nature

The soapUI Nature allows integrated access to all soapUI-functionality directly from within a Java-project. It is not complete but has been released to give an idea of how we envision working with web-services in a eclipse project.

The following example walks through a "top-down" scenario:

Step 1: Enable soapUI Nature

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 common project actions:

Step 2: Create or Import a WSDL

You can either manually create a WSDL 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 from ... " actions.

When creating the WSDL in your project, right click on the WSDL file and select "soapUI -> Add to soapUI Project"

Once imported, the WSDL is shown as a "standard" soapUI Interface node under the "soapUI Web Services" node:

Step 3: Generate Code

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)

Step 4: Implement, Deploy and Test

After implementing and deploying your Web Service to the desired container, you can now start sending web service requests "as usual"... good luck!



Next: Working with JBoss WS