1. •method to perform synchronous request-response web-services invocations
2. •method to perform synchronous one-way web-services invocations
3. •methods to perform asynchronous web-services invocations
4. •accessor to the current WS-binding associated with the runner instance
5.  
6. Here are the most relevant methods meant for performing web-services invocations, exposed by the AbstractWsRunner and by the jtr.runners.IRunnerWs interface:
7.  
8.        /**
9.      * Performs a synchronous invocation.
10.      *
11.      * @param binding The actual binding describing the web-services to invoke
12.      * @param input The message
13.      * @return The response
14.      * @throws jtr.ws.WsProviderException
15.      */
16.     public Object invoke(Binding binding, Object input) throws WsProviderException;
17.     
18.     /**
19.      * Performs a one-way webservice invocation.
20.      *
21.      * @param binding The actual binding describing the web-services to invoke
22.      * @param input The message
23.      * @throws jtr.ws.WsProviderException
24.      */
25.     public void invokeOneWay(Binding binding, Object input) throws WsProviderException;
26.     
27.     /**
28.      * Performs an asynchronous invocation.
29.      *
30.      * @param binding The actual binding describing the web-service to invoke
31.      * @param input The message
32.      * @param rl The response listener to be notified when a response becomes available
33.      * @return A reference to the <code>Future</code> instance representin the pending task
34.      * @throws jtr.ws.WsProviderException
35.      */
36.     public Future<?> invokeAsync(Binding binding, Object input, IWsResponseListener rl)
37.                      throws WsProviderException;
38.     
39.     /**
40.      * Performs an asynchronous invocation.
41.      *
42.      * @param binding The actual binding describing the web-service to invoke
43.      * @param input The message
44.      * @return A reference to the response one should poll on
45.      * @throws jtr.ws.WsProviderException
46.      */
47.     public IWsResponse invokeAsync(Binding binding, Object input) throws WsProviderException;
48.  
49. Web-Services invocations inputs & outputs
50. Input and output messages for web-services invocations are instances of classes generated by means of the xjc JAXB binding compiler, starting from a WSDL file that describes the web-service(s) we want to invoke. For example, the following instruction:
51.  
52. xjc.sh -wsdl http://localhost:8080/jtrTestBench-jtrTestBench-ejb/Arithmetical?wsdl
53.  
54. produces an output like this:
55.  
56. parsing a schema...
57. compiling a schema...
58. jtr/test/jee/ObjectFactory.java
59. jtr/test/jee/Sum.java
60. jtr/test/jee/SumResponse.java
61. jtr/test/jee/package-info.java
62.  
63. This means that all the artifacts required to marshall and unmarshall both request and response messages have been successfully generated and we can use them. If you now go back to the runner code above, you can see that these classes are actually used to prepare the input message and to represent the received response.
64.  
65. This digression on web-services input and output object classes merely serves to highlight that you can still leverage on the full JAX-WS stack, that encloses JAXB as well, for representing input and output messages. If you need further information about either JAX-WS or JAXB, please refer to their official web-pages.
66.  
67. Preparing the jtr.xml file
68. In order to have the above runner working, we need to define it into the out jtr.xml configuration file. Follows an example of how it should look like:
69.  
70. <?xml version = '1.0' encoding = 'UTF-8'?>
71.  
72. <!-- JTRunner is free software; you can redistribute it and/or modify
73.     it under the terms of the GNU General Public License as published by
74.     the Free Software Foundation; either version 2, or (at your option)
75.     any later version.
76. -->
77.  
78. <test xmlns="http://jtrunner.sourceforge.net"
79.       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
80.       xsi:schemaLocation="http://jtrunner.sourceforge.net file:./config/jtr.xsd"
81.       runs="10">
82.  
83.     <!-- JTR components factories -->
84.     <factories>

1.  
2.     <runner runs="2" binding="jboss-sum-soap-1.2">
3.         <runner-fqn>jtr.test.jee.client.WsArithmeticalTest</runner-fqn>
4.         <instance-count>2</instance-count>
5.         <parameters-assignment-policy>
6.             indexed
7.         </parameters-assignment-policy>
8.         <parameters>
9.             <param name="sleepTime" value="14" />
10.             <param name="x" value="1978" />
11.             <param name="y" value="29" />
12.         </parameters>
13.         <parameters>
14.             <param name="sleepTime" value="14" />
15.             <param name="binding" value="glassfish-sum-soap-1.2" />
16.             <param name="x" value="29" />
17.             <param name="y" value="1978" />
18.         </parameters>
19.     </runner>
20.  
21.     <bindings>
22.         <binding uniqueName="jboss-sum-soap-1.2"
23.                  serviceNameSpace="http://jee.test.jtr/"
24.                  serviceName="ArithmeticalService"
25.                  portName="ArithmeticalPort"
26.                  operationName="sum"
27.                  wsdlLoc="http://localhost:8080/jtrTestBench-jtrTestBench-ejb/Arithmetical?wsdl"
28.                  serviceMode="PAYLOAD"
29.                  jaxbObjectFactory="jtr.test.jee.arithmetical.client.ObjectFactory" />
30.  
31.         <binding uniqueName="glassfish-sum-soap-1.2"
32.                  serviceNameSpace="http://jee.test.jtr/"
33.                  serviceName="ArithmeticalService"
34.                  portName="ArithmeticalPort"
35.                  operationName="sum"
36.                  wsdlLoc="http://localhost:8181/ArithmeticalService/Arithmetical?wsdl"
37.                  serviceMode="PAYLOAD"
38.                  jaxbObjectFactory="jtr.test.jee.arithmetical.client.ObjectFactory" />
39.     </bindings>
40. </test>
41.  
42. About the binding attribute
43. Talking about the runner declaration, the only important thing to point-out is that we are using (both at the category-level and at instance-level in the second parameters-set) the binding attribute to declare that by default every WsArithmeticalTest instance must be fed with everything necessary for invoking the web-service uniquely identified by the jboss-sum-soap-1.2 name.
44. Furthermore we say that all those instances that will be injected (fed) with the second parameters-set will be enabled to invoke the web-service uniquely identified by the glassfish-sum-soap-1.2 name.
45.  
46. About the bindings and binding elements
47. In order to leverage on the JTR-runtime capabilities for invoking web-services, you must define in the jtr.xml file the web-services you want to invoke. This can be done by means of the bindings element and its binding sub-element.
48.  
49. 
50.  
51. The bindings element acts as a container of one or many binding elements, each describing a particular web-service operation to invoke.
52.  
53. Each binding element requires the following attributes to properly describe a web-service operation to be invoked:
54. •uniqueName: the unique name that identifies this binding in the jtr.xml file and that will be used as an handle by those runners willing to invoke the described web-service
55. •serviceNameSpace: the targetNameSpace found in the WSDL
56. •serviceName: the service, present in the WSDL, that contains the operation to be invoked
57. •portName: the port exposed by the service, that contains the operation to be invoked
58. •operationName: the operation to be invoked
59. •wsdlLoc: where the WSDL can be found
60. •serviceMode: whether the endpoint accesses the message or the payload. Thus legal values are MESSAGE | PAYLOAD
61. •jaxbObjectFactory: the JAXB-generated class capable of producing input and output messages conforming with the grammar expressed in the WSDL