07 November 2008 - 2.5-beta2 user guide blog eclipse intellij netbeans maven PDF files forums bugs sourceforge eviware.com


Eviware Logo

Code Generation Tools for Web Services

The following code generation tools have currently been integrated and are available from the main Tools menu or form the Interface right-button menu: JBossWS WSTools, JBossWS WSConsume, JAX-RPC, JAX-WS, Axis 1.X, Axis 2, CXF 2.X, XFire 1.X, Oracle wsa, XmlBeans 2.X, JAXB 2.X, GSoap 2.X and .NET 2.0.

Each integration has a number of tabs for configuring the corresponding tools options and adding arbitrary command line arguments. If the tool is invoked from the Interface menu, relevant values will be pre entered into the dialogs (WSDL URL, Namespaces, etc.) and the integrations remember their settings, making it easy to rerun the desired tools if changes are made to the external sources or WSDLs.

If the WSDL for the current interface has been cached, an option will be available for using either the cached WSDL or the "online" WSDL. If selecting to use the cached WSDL, soapUI will first export the WSDL to a temporary directory and specify this location as the WSDL path.

Support for several different Code Generation tools in soapUITools menu: Support for several different Code Generation tools in soapUI

Custom Arguments for Code Generation

All integrations have a "Custom args" tab allowing the specification of custom arguments to the invoked tool(s), for example those that are not supported by soapUI in intermediate versions (before we catch up :-). The following dialog for the XFire integration allows both custom args to java and to the WsGen tool itself:

Setting Custom arguments for Code Generation

Running a tool

Once the tool is configured as required by its dialog, a "Generate" option will open a separate window showing the input or output of the invoked tools process. During the process execution a "Cancel" button will be available for canceling the ongoing process, otherwise a success/error message will be shown when the tool is finished. The log window will be available until it is closed allowing detailed viewing of the process output (for debugging purposes...). The following image shows the process runner window after a successful invocation to the JWSDP WSCompile tool:

Running a code generation tool

JBossWS WSTools Integration

ToolVersion(s)DocumentationInstallation / Usage
JBossWS wstoolsversions 1.0.XJBossWS User GuideInstall the latest JBossWS stack and install/configure as required. Specify the directory containing the wstools script in the Tool Integrations settings dialog. The dialog has a "Show Config" button that displays the wstools config file generated for the current settings.

JBossWS WSConsume Integration

ToolVersion(s)DocumentationInstallation / Usage
JBossWS wstoolsversions 1.0.XJBossWS User GuideInstall the latest JBossWS 1.2 or newer stack and install/configure as required. Specify the directory containing the WSTools script in the Tool Integrations settings dialog. The dialog has a "Show Config" button that displays the WSTools config file generated for the current settings.

JWSDP JAX-RPC/wscompile Integration

ToolVersion(s)DocumentationInstallation / Usage
JWSDP JAX-RPC / WSCompile, tested with versions 1.6 and 2.0tested with versions 1.6 and 2.0WSCompileInstall the desired JWSDP version and install/configure as required. Specify the directory containing the WSCompile script in the Tool Integrations settings dialog.

JWSDP JAX-WS WSImport

ToolVersion(s)DocumentationInstallation / Usage
JWSDP JAX-WS / WSImport, tested with versions 1.6 and 2.0tested with versions 1.6 and 2.0WSImportInstall the desired JWSDP version and specify the jaxWS / bin directory in the soapUI Tool Integrations settings

Apache Axis 1.X

ToolVersion(s)DocumentationInstallation / Usage
Apache Axis 1.Xtested with versions 1.2.1, 1.3 and 1.4wsdl2javaInstall Axis 1.X and specify the installation directory in the soapUI Tool Integrations settings

Apache Axis 2

ToolVersion(s)DocumentationInstallation / Usage
Apache Axis 2tested with 0.9X and 1.0wsdl2javaInstall Axis 2 and specify the installation directory in the soapUI Tool Integrations settings

Apache CXF 2.X

ToolVersion(s)DocumentationInstallation / Usage
Apache CXF 2.0tested with 2.0.1wsdl2javaInstall CXF and specify the installation directory in the soapUI Tool Integrations settings

XFire 1.X

ToolVersion(s)DocumentationInstallation / Usage
XFire 1.X WsGentested with 1.XWsGenInstall XFire 1.X and specify the installation directory in the soapUI Tool Integrations settings

Oracle wsa

ToolVersion(s)DocumentationInstallation / Usage
Oracle wsa.jartested with latest JDeveloper releaseOracle Web Services (PDF)Install JDeveloper and specify <jdeveloper-root>/webservices/lib in soapUI Tool Integrations settings

XMLBeans 2.x

ToolVersion(s)DocumentationInstallation / Usage
XMLBeans 2.Xtested with 2.2.0scompInstall XmlBeans 2.X and specify the installation directory in the soapUI Tool Integrations settings

JAXB 2.x

ToolVersion(s)DocumentationInstallation / Usage
JWSDP JAXB 2.0tested with JWSDP 2.0xjcInstall JWSDP as required and specify the jaxb\bin installation directory in the soapUI Tool Integrations settings

GSoap 2.X

ToolVersion(s)DocumentationInstallation / Usage
GSoap 2.Xtested with GSoap 2.7 on win32wsdl2h, soapcpp2Install GSoap as required and specify the installation directory in the soapUI Tool Integrations settings

.NET 2.0

ToolVersion(s)DocumentationInstallation / Usage
.NET 2.0.NET 2.0wsdl.exeInstall Visual Studio and .NET 2.0 and specify the directory containing wsdl.exe in the soapUI Tool Integrations settings


Next: Apache TCPMon