soapUI: General Questions

• When should I use soapUI?
  Use it when you are developing/discovering Web Service clients or implementations and need a tool to test them interactively and/or create functional and load tests that can be run in a continuous integration environment.
• What can't I do with soapUI?
  Some of the more obvious missing features are WSDL authoring WS-Security support. Check out the Future Plans document to see what's missing (for now).
• Does soapUI work with any Web Service technology?
  soapUI is platform agnostic, you can use it for Web Services created with .NET, J2EE, Perl, PHP, etc. The only requirements on your Web Service are that they have a defining WSDL, that they are bound with the SOAP/HTTP binding, and that they do not use SOAP-Encoding (if you want to do validations)

soapUI Distribution and Execution

• Why would I use the Java WebStart distribution?
  Because it is easier to install and update. You won't have to download new versions and bug-fixes, the Java WebStart runtime does that for you. Also, minor updates/fixes will be added to the WebStart distribution continuously, whereas the offline distribution will be updated at relevant intervals.
• Are there any differences between the Java WebStart distribution and the standalone distribution?
  There are some differences:
  1) The standalone distribution allows you to specify the workspace file as a command-line argument to soapUI
  2) The WebStart classloader handling will prevent you from performing sandboxed operations from within your Groovy scripts
• Does the Java WebStart distribution require me to be online when I want to use soapUI?
  No, soapUI can run in offline mode. You may need to setup a start-icon for soapUI though (using the Java control panel).

soapUI Usage

• How do I save the changes I make to my projects, requests, TestCases, etc?
  soapUI automatically saves everything on exit. If you want to save your projects without exiting (for example if you want to commit your project file to CVS) use the "Save All" option in the main File menu
• I have updated my XML Schema for my service but soapUI still generates/validates according to the old schema
  soapUI caches XML schemas when they are first loaded. If you need to force a reload of an interfaces schema either restart soapUI or use the "Update Definition" action for an interface and just specify the same URL as the current one.