Version 4

    Quick Overview

    The GUI is basically a fully dynamic, single page webapp for quickly invoking webservice endpoints without the need of generating and compiling client stubs or directly writing SOAP xml messages.

    You start by typing the URL of the wsdl contract you want to consume (you can provide username and password if required, http basic auth only supported atm):

     

    wise-gui-img1.png

     

    then you click on "OK" button and let Wise fetch the wsdl, parse it together with any referenced schema and finally present you a list of available endpoint operations:

     

    wise-gui-img2.png

     

    you select an operation and Wise shows a tree representing the input parameters for that:

     

    wise-gui-img3.png

     

    you can fill in input boxes with data, enable/disable elements (for nillable ones only) and add/remove elements for collection and list parameters. Finally, you click on "Perform invocation" button and get another tree for the result object:

     

    wise-gui-img4.png

     

    That's all, very simple, yet really effective and quick solution for testing ws endpoints. No need for either writing a single line of code or playing with XML. No external tool needed (besides for your browser). And possibly even more interesting, no special technical knowledge required, so e.g a business analyst might validate WS service results without bugging the developer who worked on it ;-) (keep in mind that in most scenarios, exposing a simple test WS endpoint is basically a matter of adding a single @WebService annotation on a POJO or EJB3 class...)

     

    Building and installing

    You need to download the sources from the download page. Then make sure the JBoss.org Maven repository is properly setup.

    Then unpack the downloaded archive, start JBoss AS 7 (7.1.0 or greater) and simply run:

    mvn clean package jboss-as:deploy
    

    Finally start your favorite browse and hit http://localhost:8080/wise-gui address (assuming JBoss AS is bound to localhost:8080)

    The application is undeployed by running:

    mvn jboss-as:undeploy