EventService -- Help SourceForge
This is an experimental text fixture for monitoring and tuning the public web services hosted at "".
Some of the capabilities of this test fixture:
Select the tab 'Overview' for data about the exposed public service
Select the tab 'Console' for more data
Select the tab 'TestForm' or 'TestXML' to execute the tests

The Overview tab displays public information about the services, including:
  • The WSDL that describes the exposure of the web services.
    Clients of the web service use the WSDL file to determine how to call the web services and what data will be returned. The WSDL exposes both methods and callbacks on the services.
  • The service description, including the service's available methods and callbacks.
The Console tab displays private information about your service, including:
  • How the service is implemented.
  • Pushbuttons to clear the conversation state and logs for the services.
The Test Form tab provides a simple test environment for public methods:
  • You can provide parameters for a method and examine its return value. You can also track and test the different parts of a conversation. To start the test, click on the Start button.
  • Information about the service request and response, including the XML message returned.
  • The conversation ID that appears in the Message Log sub-window uniquely identifies each conversation that is underway. Click on the ID to select this conversation. You can view the results for each method or callback that has participated in this conversation by clicking on its name in the list. Click the Refresh link to refresh the message log.
The Test XML tab shows XML data sent to your service.
  • If your method takes parameters of a data type other than String, you must modify the parameter placeholders in the SOAP body before you click the button to call the method. For example, if your method expects an integer, you must supply a valid integer in the SOAP body.

Disclaimer:   The general scheme and much of the descriptive commentary on these pages was stolen shamelessly from BEA WebLogic Workshop (TM) .
This looks like a very useful testing approach and is worthy of emulation.