An unlimited number of requests can be added to an operation in soapui. Each request can have its own SOAP Request, endpoint, encoding, etc. Requests are mainly managed through the request-editor displayed when double-clicking a request node in the navigator (described below)
The following actions are available from the request nodes' right-button menu:
|
![]() |
The "Details" tab shown in the bottom-left shows the following values when a Request node is selected in
the navigation tree
|
![]() |
The request editor is more or less the main window in soapui, both for request and for test-requests. It is divided into a left request-area and a right response-area; submitting the requests posts it to its endpoint and displays the result in the right area.
When moving focus to one of the editors, the dividing splitpane will automatically be moved to give the focused editor a larger visible area, diminishing the requirement to resize the splitpane manually when working with request/response messages.
The request/response xml-editors support syntax-hightlighting, undo/redo, copy/paste, etc.
The following actions are available from the request/response editors right-button menu:
|
![]() |
When submitting a request using either the submit toolbar button or the Alt-Enter editor action, the request message is sent to the selected endpoint using the specified encoding. Submittal is done in a background thread so any number of requests can be running simultaneously (an animated icon in the navigator shows that they are running).
If the service requires authentication, soapui will attempt to authenticate using the
specified username/password/domain values. Currently supported authentication types are those supported
by HttpClient, ie Basic, Digest and NTLM authentication. SSL should work (=not tested!) if you
use https
urls and install JSSE
accordingly.
During submittal, the request/response editors are made read-only and all actions except the cancel button in the toolbar are disabled. One can cancel an ongoing request either by a toolbar button or by pressing Alt-X in one of the editors. If you choose to close the editor window while a request is running, you will be prompted if you first want to cancel the ongoing request. Depending on the state of the request, its thread may actually continue in the background even though soapui shows it as canceled, but from a useability point-of-view, you should never notice.
Once a response has been received, it will be displayed in the response area and a log message will be displayed in the soapui log view and the request editors status bar showing the time taken and size of the received response. If you choose to close the request editor without cancelling an ongoing request, the response will be shown in the response area when the request editor is made visible again.
The request-editor toolbar has the following actions (from left to right)
When pressing Alt-V in either the request or response area, the contained message is validated for valid
xml and against its operations message definition.
Validation errors are shown in a list-box displayed under the editor. Double-clicking an error will move the corresponding editor caret to the line of the error (if possible). If the message is valid the error-list is hidden and an Ok-message is displayed. Validation is currently only supported for literal-encoded messages (both rpc and document), SOAP-encoded messages are not supported. |
![]() |