06 August 2007 - 1.7.5 | home user-guide eclipse jbossws intellij netbeans maven 1.X/2.X PDF files forums bugs sourceforge

Home
Getting Started
User Guide

- Overview
  - Tabbed Desktop
  - License Management
  - Preferences
  - XPath Selection
  - Script Library
- Workspaces
- Projects
- Interfaces
  - Interface Viewer
- Operations
- Working with Requests
  - Form Editor
  - Outline Editor
  - Message Inspectors
  - Attachments/Inline Files
- Functional Testing
  - Getting Started
  - TestSuites
  - TestCases
    - Test Requests
      - Assertions
      - Editor Wizards
    - Property Transfers
    - Conditional Gotos
    - Groovy Scripts
      - Examples
      - GroovyUtils
    - Properties Step
    - Delay Step
    - Mock Response
    - DataSource
    - DataSource Loop
  - Property Expansion
- Load Testing
  - Getting Started
  - Limit & Strategies
  - Execution
  - Assertions
  - Diagrams
  - JMeter comparison
- Mocking
  - Getting Started
  - Mock Services
  - Mock Operations
  - Mock Responses
- Usage Scenarios
  - Data-Driven Testing
  - Template-Driven Testing
  - Interactive Testing
  - Surveillance Testing
- Tool Integrations
  - Code Generation
  - WSDL Generation
  - WS-I Tools
  - Apache Tcp-Mon
- CommandLine Tools
  - TestCaseRunner
  - LoadTestRunner
  - MockServiceRunner
  - ToolRunner
- Keyboard shortcuts

IDE/Tool Plugins
Search soapUI site
Project Documentation

- About soapUI
- Project Info
- Project Reports

## SoapUIToolRunner

The SoapUIToolRunner can be used to any of the integrated Code Generation tools from the command-line as they have been configured in soapUI.

The runner is defined in the `com.eviware.soapui.tools.SoapUIToolRunner` class and takes the path to the soapUI project file containing the interface and tool-configuration to run. It has the following options:

switch | description
--- | ---
i | the interface for which the tool should be run
t | the tool(s) to run, a comma-seperated list with the following tokens; axis1, axis2, dotnet, gsoap, jaxb, wstools, wsconsume, ora, wsi, wscompile, wsimport, xfire or xmlbeans
s | the soapui-settings.xml file to use (usually the one in the soapUI bin directory)

The distribution contains a toolrunner.bat script for running tools from within the bin directory, for example;

    toolrunner.bat -iAWSECommerceServicePortType -taxis1 G:\test\Amazon-soapui-project.xml

will run all the axis 1.X code-generation as previously defined within soapUI and produce the following output:

    SoapUI 1.6 beta1 Tool Runner
    02:27:02,386 DEBUG [SoapUI] initialized soapui-settings from [soapui-settings.xml]
    02:27:02,506 INFO  [WsdlProject] Loaded project from [G:\test\Amazon-soapui-project.xml]
    02:27:08,765 INFO  [SoapUIToolRunner] Running tools for project [Amazon]
    directory: C:\java\axis-1_4\lib
    command: java -cp activation.jar;axis-ant.jar;axis.jar;bsf.jar;castor-0.9.5.2.jar;commons-codec-1.2.jar;
     commons-discovery-0.2.jar;commons-httpclient-3.0-rc2.jar;commons-logging-1.0.4.jar;commons-net-1.0.0-dev.jar;
     httpunit.jar;ibmjsse.jar;javax.jms.jar;jaxrpc.jar;JimiProClasses.jar;junit-3.8.1.jar;log4j-1.2.8.jar;
     mailapi_1_3_1.jar;saaj.jar;servlet.jar;wsdl4j-1.5.1.jar org.apache.axis.wsdl.WSDL2Java -v -W -s -a
     -H -T 1.2 -o g:\test\amazon C:\DOCUME~1\OLE~1.MAT\LOCALS~1\Temp\tempdir8304.tmp\AWSECommerceService.wsdl
    Parsing XML file:  C:\DOCUME~1\OLE~1.MAT\LOCALS~1\Temp\tempdir8304.tmp\AWSECommerceService.wsdl
    Generating g:\test\amazon\com\amazon\webservices\AWSECommerceService\_2006_05_17\CartGetRequest.java
    ...
    Generating g:\test\amazon\com\amazon\webservices\AWSECommerceService\_2006_05_17\deploy.wsdd
    Generating g:\test\amazon\com\amazon\webservices\AWSECommerceService\_2006_05_17\undeploy.wsdd
    SoapUIToolRunner: Execution finished successfully
    02:27:14,593 INFO  [SoapUIToolRunner] time taken: 5814ms

The above axis 1.X generation had been previously configured in soapUI as shown below:

Next: Keyboard shortcuts