nmukhi 2002/12/11 12:49:16
Modified: java/samples/localjava/client/stub README.html
Log:
Minor edits
Revision Changes Path
1.2 +6 -7 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.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README.html 11 Dec 2002 20:38:40 -0000 1.1
+++ README.html 11 Dec 2002 20:49:16 -0000 1.2
@@ -17,14 +17,13 @@
<li>A JAXP compliant XML parser, such as Xerces</li>
<li>wsdl4j.jar</li>
<li>qname.jar</li>
- <li>axis.jar (since by default WSIF uses its Axis provider to invoke SOAP
services)</li>
- <li>JAR files required by Axis - log4j.jar, commons-logging.jar, jaxrpc.jar,
saaj.jar</li>
</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 and the symbol for the company whose stock quote you are
interested in. For example, <br>
-<tt>java samples.SimpleSOAP.client.static.Run
file:/mywsifinstallation/samples/SimpleSOAP/StockquoteSOAP.wsdl IBM</tt></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 ../../StockquoteSOAP.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>
+<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>
+<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>
+After the tool finished running, we deleted all the generated files except
<tt>AddressBook.java</tt> (this is the java interface corresponding to the port type),
<tt>Address.java</tt> and <tt>Phone.java</tt> (these two are the java representations
of the complex schema types used in the sample).</p>
<hr width="100%">
</body></html>
