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.
The following actions are available from the workspace-nodes right-button
menu (and from the main "File" menu):
|
![]() |
Internally, soapui abstracts the actual nature of projects and their contained interfaces, tests, etc..
opening for support of 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). 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:
|
![]() |