You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by nm...@apache.org on 2003/01/07 18:52:44 UTC

cvs commit: xml-axis-wsif/java/samples/multibinding/client/stub README.html

nmukhi      2003/01/07 09:52:44

  Modified:    java/samples/customfactory/client/dynamic README.html
               java/samples/ejb/client/dynamic README.html
               java/samples/localjava/client/stub README.html
               java/samples/multibinding/client/dynamic README.html
               java/samples/multibinding/client/stub README.html
  Log:
  Minor changes to READMEs (typos etc.)
  
  Revision  Changes    Path
  1.2       +1 -1      xml-axis-wsif/java/samples/customfactory/client/dynamic/README.html
  
  Index: README.html
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/samples/customfactory/client/dynamic/README.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- README.html	20 Dec 2002 12:53:22 -0000	1.1
  +++ README.html	7 Jan 2003 17:52:43 -0000	1.2
  @@ -10,7 +10,7 @@
   <h2>
   Web Services Invocation Framework:<br>
   Invoking the CustomFactory Sample using WSIF's dynamic invocation interface</h2>
  -<p>After you have <a href="../../../../doc/samples.html">set up the CLASSPATH in your environment</a>, to invoke this sample using WSIF's DII, run the DynamicInvoker class. Specify as command line arguments the location of the WSDL file for the stockquote sample followed by the operation you wish to invoke and the symbol for the company whose stockquote you are interested in. For example, <br><tt>java  clients.DynamicInvoker samples/simplesoap/StockquoteSOAP.wsdl getQuote IBM</tt></p>
  +<p>After you have <a href="../../../../doc/samples.html">set up the CLASSPATH in your environment</a>, to invoke this sample using WSIF's DII, run the DynamicInvoker class. Specify as command line arguments the location of the WSDL file for the stockquote sample followed by the operation you wish to invoke and the symbol for the company whose stockquote you are interested in. For example, <br><tt>java  clients.DynamicInvoker samples/customfactory/StockquoteSOAP.wsdl getQuote IBM</tt></p>
   <p>To see details of how the WSIF API is used to make invocations dynamically, take a look at the code for the <a href="../../../clients/DynamicInvoker.java">DynamicInvoker class</a>.</p>
   <hr width="100%">
   </body></html>
  
  
  
  1.2       +1 -1      xml-axis-wsif/java/samples/ejb/client/dynamic/README.html
  
  Index: README.html
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/samples/ejb/client/dynamic/README.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- README.html	13 Dec 2002 22:59:55 -0000	1.1
  +++ README.html	7 Jan 2003 17:52:43 -0000	1.2
  @@ -12,7 +12,7 @@
   Invoking the EJB Sample using WSIF's dynamic invocation interface</h2>
   <p>First you need to <a href="../../../../doc/samples.html">set up the CLASSPATH in your environment</a>. Beyond the standard classpath setting, you also need to add the J2EE client jar files to your classpath. The set of J2EE client JARs is vendor specific; refer to the documentation in your application server on how to set up the environment for an EJB client, and add the JAR files specified. For JBoss users, we have included a script to set up the client environment. To run this script, make sure you are in your base WSIF directory (the one that contains the <tt>classpath.bat</tt> script. Set the variable <tt>JBOSS_HOME</tt> to point to your JBoss installation. From there, run the command <tt>samples\ejb\client\jboss_setup\jboss.bat</tt>. This sets up the entire client classpath required to run the sample using JBoss client JAR files.</p>
   <p>The <a href="../../AddressBook.wsdl">WSDL file</a> that describes the service and its EJB binding is vendor-specific in the <tt>&lt;ejb:address&gt;</tt> element. The <tt>initialContextFactory</tt>, <tt>jndiName</tt> and <tt>jndiProviderURL</tt> attributes will all depend on your specific deployment; refer to your application server documentation on how to write an EJB client to learn more about JNDI and related issues. Make sure these values are all correct before you try running the client.</p>
  -<p>After you have set up your classpath, to invoke this sample using WSIF's DII, run the <tt>Run</tt> class located in this directory. This class will populate an addressbook with two names and then query each of them by invoking various operations supported by the service. To run this class, specify on the command line the location of the WSDL file for the service. For example, <br><tt>java ejb.clients.dynamic.Run samples/ejb/AddressBook.wsdl</tt></p>
  +<p>After you have set up your classpath, to invoke this sample using WSIF's DII, run the <tt>Run</tt> class located in this directory. This class will populate an addressbook with two names and then query each of them by invoking various operations supported by the service. To run this class, specify on the command line the location of the WSDL file for the service. For example, <br><tt>java ejb.client.dynamic.Run samples/ejb/AddressBook.wsdl</tt></p>
   <p>Look at the code in the <tt>Run.java</tt> file in this directory to see how to use WSIF's DII yourself. Note that the <tt>DynamicInvoker</tt> class we used to <a href="../../../simplesoap/client/dynamic/README.html">invoke the simplesoap sample dynamically</a> cannot be used for this one since the <tt>DynamicInvoker</tt> as it stands now is limited to invocation of services using primitive schema types only.</p>
   <hr width="100%">
   </body></html>
  
  
  
  1.3       +1 -1      xml-axis-wsif/java/samples/localjava/client/stub/README.html
  
  Index: README.html
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/samples/localjava/client/stub/README.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- README.html	11 Dec 2002 20:49:16 -0000	1.2
  +++ README.html	7 Jan 2003 17:52:43 -0000	1.3
  @@ -20,7 +20,7 @@
   </ul>
   </p>
   <p>This directory contains a file called <tt>Run.java</tt> that contains the <tt>main</tt> method. This is the logic that uses the generated stub interface to run the sample. So you can run this class, specifying on the command line the location of the WSDL file for the sample. For example, <br>
  -<tt>java samples.localjava.client.stub.Run samples/localjava/AddressBook.wsdl</tt></p>
  +<tt>java localjava.client.stub.Run samples/localjava/AddressBook.wsdl</tt></p>
   <p>The sample code will use the stub interface to populate an addressbook with two entries and will then query the addressbook for those two addresses using the corresponding names.</p>
   <p>To generate the stub interface, you can use any tool that generates Java interfaces for WSDL services using their port type descriptions, such as WSDL2Java from Axis. WSIF assumes a correspondence between the generated Java interface and the WSDL port type that has its abstract description as specified in the JAX-RPC specification. This particular sample did not use WSDL2Java in a simple way (due to a current bug in WSDL2Java that prevents it from processing WSDLs that do not have a valid SOAP endpoint or binding. We managed to get it to work by commenting out the java binding that is currently there, and introducing a binding element that describes a SOAP binding. After doing this, we ran WSDL2Java in the following way:<br>
   <tt>java org.apache.axis.wsdl.WSDL2Java ../../AddressBook.wsdl</tt><br>
  
  
  
  1.2       +6 -4      xml-axis-wsif/java/samples/multibinding/client/dynamic/README.html
  
  Index: README.html
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/samples/multibinding/client/dynamic/README.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- README.html	17 Dec 2002 17:14:12 -0000	1.1
  +++ README.html	7 Jan 2003 17:52:43 -0000	1.2
  @@ -11,10 +11,12 @@
   Web Services Invocation Framework:<br>
   Invoking the MultiBinding Sample using WSIF's dynamic invocation interface</h2>
   <p>After you have <a href="../../../../doc/samples.html">set up the CLASSPATH in your environment</a>, to invoke this sample using WSIF's DII, run the DynamicInvoker class. Specify as command line arguments the location of the WSDL file for the multibinding sample followed by the operation you wish to invoke, an optional preferred port in parentheses and the symbol for the company whose stockquote you are interested in. For example, 
  -<br>Invocation with no port preference: <tt>java  clients.DynamicInvoker samples/simplesoap/StockquoteSOAP.wsdl getQuote IBM</tt>
  -<br>Invocation with SOAP port preference: <tt>java  clients.DynamicInvoker samples/simplesoap/StockquoteSOAP.wsdl getQuote(StockQuoteSOAPPort) IBM</tt>
  -<br>Invocation with java port preference: <tt>java  clients.DynamicInvoker samples/simplesoap/StockquoteSOAP.wsdl getQuote(StockQuoteJavaPort) IBM</tt>
  +<br>Invocation with no port preference: <tt>java  clients.DynamicInvoker samples/multibinding/StockQuoteService.wsdl getQuote IBM</tt>
  +<br>Invocation with SOAP port preference: <tt>java  clients.DynamicInvoker samples/multibinding/StockQuoteService.wsdl getQuote(StockQuoteSOAPPort) IBM</tt>
  +<br>Invocation with java port preference: <tt>java  clients.DynamicInvoker samples/multibinding/StockQuoteService.wsdl getQuote(StockQuoteJavaPort) IBM</tt>
   </p>
   <p>To see details of how the WSIF API is used to make invocations dynamically, take a look at the code for the <a href="../../../clients/DynamicInvoker.java">DynamicInvoker class</a>. Note the use of the <tt>portName</tt> parameter to make the invocation using the selected port.</p>
   <hr width="100%">
  -</body></html>
  \ No newline at end of file
  +</body></html>
  +
  +WRONG FILE
  \ No newline at end of file
  
  
  
  1.2       +3 -5      xml-axis-wsif/java/samples/multibinding/client/stub/README.html
  
  Index: README.html
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/samples/multibinding/client/stub/README.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- README.html	17 Dec 2002 17:14:12 -0000	1.1
  +++ README.html	7 Jan 2003 17:52:43 -0000	1.2
  @@ -12,16 +12,14 @@
   Invoking the Multibinding Sample through a high level stub interface</h2>
   First, you must <a href="../../../../doc/samples.html">set up the CLASSPATH in your environment</a>.
   <p>This directory contains a file called <tt>Run.java</tt> that contains the <tt>main</tt> method. This is the logic that uses the generated stub interface to run the sample. So you can run this class, specifying on the command line the location of the WSDL file for the sample, the symbol for the company whose stock quote you are interested in and an optional port preference. For example, 
  -<br>Invoking the service without specifying any port preference:
  -<tt>java multibinding.client.stub.Run samples/multibinding/StockquoteSOAP.wsdl IBM</tt>
   <br>Invoking the service with the SOAP port preference:
  -<tt>java multibinding.client.stub.Run samples/multibinding/StockquoteSOAP.wsdl IBM StockQuoteSOAPPort</tt>
  +<tt>java multibinding.client.stub.Run samples/multibinding/StockquoteService.wsdl IBM StockQuoteSOAPPort</tt>
   <br>Invoking the service with the java port preference:
  -<tt>java multibinding.client.stub.Run samples/multibinding/StockquoteSOAP.wsdl IBM StockQuoteJavaPort</tt>
  +<tt>java multibinding.client.stub.Run samples/multibinding/StockquoteService.wsdl IBM StockQuoteJavaPort</tt>
   </p>
   <p>The WSIF API allows programs to choose a preferred port when getting a reference to the stub interface. Any calls made via that stub interface will then use the selected port and its associated binding protocol. See the <tt>Run.java</tt> code for details.</p>
   <p>To generate the stub interface, you can use any tool that generates Java interfaces for WSDL services using their port type descriptions, such as WSDL2Java from Axis. WSIF assumes a correspondence between the generated Java interface and the WSDL port type that has its abstract description as specified in the JAX-RPC specification. This particular sample used WSDL2Java in the following way:<br>
   <tt>java org.apache.axis.wsdl.WSDL2Java ../../StockquoteService.wsdl</tt><br>
   After the tool finished running, we deleted all the generated files except <tt>NetXmethodsServicesStockquoteStockQuotePortType.java</tt> (this is the java interface corresponding to the port type and is all that is required by WSIF).</p>
   <hr width="100%">
  -</body></html>
  \ No newline at end of file
  +</body></html>