10 April 2007 - 1.7 |
soapUI uses the same workspace/project metaphor as for example eclipse:
${user.home}/default-soapui-workspace.xml
file.
If you want to use multiple workspaces specify another filename (for example "my-soapui-workspace.xml") as
the only command-line argument to soapUI, the corresponding file will be created/used instead.
When starting, soapUI loads all project files contained in the current workspace and displays these
as project nodes in the navigator. If a project file is for some reason not available it will be grayed out and displayed as disabled, with right-click options to either remove it from the workspace or reload it (optionally from a new location). | ![]() |
When exiting, soapUI will automatically save all project files in the workspace. If soapUI detects that a project file has been modified externally since it was last loaded (based on modification date), it will first prompt if to overwrite the file or leave it as it is.
The following actions are available from the workspace-nodes right-button
menu (and from the main "File" menu):
| ![]() |
The "Details" tab shown in the bottom-left shows the following values when the workspace node is selected in
the navigation tree
| ![]() |
Selecting the New WSDL Project option opens this dialog which prompts for:
Once specified, soapUI will prompt for a filename to which the project is to be saved (defaults to
<project-name>-soapui-project.xml
). Put this file anywhere you want, te file
is a regular XML file and can be checked into SCM systems and edited with any XML editor.
Internally, soapUI abstracts the actual nature of projects and their contained interfaces, tests, etc...
opening the possiblity of support for other service-definitions/protocols than WSDL/SOAP (check out
the com.eviware.soapui.model
package). Currently though, the only implementation for
these interfaces is for WSDL 1.1 and the SOAP/HTTP binding (as required by Basic Profile 1.0). Therefore,
all actions and functionality described will be in regard to this implementation.
A soapUI WSDL project contains the following items:
soapUI projects are saved in a self contained xml-file upon creation (as described above). This file can be safely moved around, checked into CVS, sent by email, etc. It only has file-system references if an interface/WSDL has been imported from a local file (not recommended due to this limitation) and/or if referenced attachments / inline files are used (see Attachments). When obtaining an existing soapUI project file, this can be added to the current workspace with the "Import Project" workspace action as described above
The following actions are available from the project nodes' right-button menu:
| ![]() |
The "Details" tab shown in the bottom-left shows the following values when the workspace node is selected in
the navigation tree
| ![]() |