axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nmu...@apache.org
Subject cvs commit: xml-axis-wsif/java/samples/simplesoap/client/stub README.html
Date Wed, 11 Dec 2002 20:36:14 GMT
nmukhi      2002/12/11 12:36:14

  Modified:    java/samples/complexsoap/client/dynamic README.html
               java/samples/complexsoap/client/stub README.html
               java/samples/localjava README.html
               java/samples/simplesoap/client/dynamic README.html
               java/samples/simplesoap/client/stub README.html
  Removed:     java/samples/addressbook/wsifservice AddressBook.java
                        AddressBook.wsdl DeploymentDescriptor.xml
                        README.txt
               java/samples/addressbook/wsiftypes Address.java
                        AddressBook.java Phone.java
               java/samples/clients/addressbook Main.java README.txt
  Log:
  Minor changes to sample READMEs
  Removed old addressbook sample; interferes with new sample that uses same WSDL
  
  Revision  Changes    Path
  1.2       +1 -1      xml-axis-wsif/java/samples/complexsoap/client/dynamic/README.html
  
  Index: README.html
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/samples/complexsoap/client/dynamic/README.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- README.html	10 Dec 2002 11:03:26 -0000	1.1
  +++ README.html	11 Dec 2002 20:36:14 -0000	1.2
  @@ -21,7 +21,7 @@
     <li>JAR files required by Axis - log4j.jar, commons-logging.jar, commons-discovery.jar,
jaxrpc.jar, saaj.jar</li>
   </ul>
   </p>
  -<p>After you have set up the CLASSPATH in your environment, to invoke this sample
using WSIF's DII, run the <tt>Run</tt> class located in this directory. Specify
as command line arguments the location of the WSDL file for the service and the zip code you
are interested in. For example, <br><tt>java samples.ComplexSOAP.clients.dynamic.Run
file:/mywsifinstallation/samples/ComplexSOAP/Zip2Geo.wsdl 10005</tt></p>
  +<p>After you have set up the CLASSPATH in your environment, to invoke this sample
using WSIF's DII, run the <tt>Run</tt> class located in this directory. Specify
as command line arguments the location of the WSDL file for the service and the zip code you
are interested in. For example, <br><tt>java samples.ComplexSOAP.clients.dynamic.Run
samples/complexsoap/Zip2Geo.wsdl 10005</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.2       +1 -1      xml-axis-wsif/java/samples/complexsoap/client/stub/README.html
  
  Index: README.html
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/samples/complexsoap/client/stub/README.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- README.html	10 Dec 2002 11:03:26 -0000	1.1
  +++ README.html	11 Dec 2002 20:36:14 -0000	1.2
  @@ -22,7 +22,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 followed by the zip code of interest. For example, <br>
  -<tt>java file:/mywsifinstallation/samples/ComplexSOAP/Zip2Geo.wsdl samples.ComplexSOAP.client.static.Run
10005</tt></p>
  +<tt>java samples/complexsoap/Zip2Geo.wsdl samples.complexsoap.client.stub.Run 10005</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 ../../Zip2Geo.wsdl</tt><br>
   After the tool finished running, we deleted all the generated files except <tt>Zip2GeoSoap.java</tt>
and <tt>LatLongReturn.java</tt> (Zip2GeoSoap is the java interface corresponding
to the port type; LatLongReturn is the java representation of the complex schema type returned
by the service - that is all that is required by WSIF). Note that the WSIF provider (in this
case, Axis) automatically handles (de)serialization of the data that the user's code sees.</p>
  
  
  
  1.2       +2 -2      xml-axis-wsif/java/samples/localjava/README.html
  
  Index: README.html
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/samples/localjava/README.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- README.html	11 Dec 2002 15:57:31 -0000	1.1
  +++ README.html	11 Dec 2002 20:36:14 -0000	1.2
  @@ -10,9 +10,9 @@
   <h1>
   Web Services Invocation Framework:<br>
   Java Sample</h1>
  -<p>This sample aims to demonstrate the invocation of the local java class through
WSIF's API. Why would one want to do this, you ask. The main reason is that having a uniform
view of software through WSDL necessitates this. It is also useful when developing a web service
- you write your web service in java, expose it through WSDL with a java binding. Then you
can test this using a client that employs WSIF's API to invoke the service. Since you are
really using a java class, there is nothing to deploy, no web server to stop and start, etc.
When you are satisfied that the functionality works, you can replace the binding in the WSDL
with a SOAP binding, deploy the service as a SOAP service and retest with your client - which
you don't need to change at all. Following this path in your Web services development reduces
debugging pains one usually has with SOAP services, by making sure the basic functionality
works before moving to a SOAP binding.</p>
  +<p>This sample aims to demonstrate the invocation of the local java class through
WSIF's API. Why would one want to do this, you ask? The main reason is that having a uniform
view of software through WSDL necessitates this. It is also useful when developing a web service
- you write your web service in java, expose it through WSDL with a java binding. Then you
can test this using a client that employs WSIF's API to invoke the service. Since you are
really using a java class, there is nothing to deploy, no web server to stop and start, etc.
When you are satisfied that the functionality works, you can replace the binding in the WSDL
with a SOAP binding, deploy the service as a SOAP service and retest with your client - which
you don't need to change at all. Following this path in your Web services development reduces
debugging pains one usually has with SOAP services, by making sure the basic functionality
works before moving to a SOAP binding.</p>
   <p>In this particular sample, we describe an AddressBook service. For those unfamilar
with it, this service offers a port type with three operations. Two of the operations add
an entry to the address book, using slightly different styles for providing input information.
The third operation queries the address book with a name. The service uses complex schema
types for representing an address and a phone number.</p>
  -<p>The abstract functionality is tied to a java binding which describes how a java
class supports the abstract port type defined. This isn't a standard WSDL binding, instead
this binding is defined as a part of WSIF; you can find details on how to write a java binding
<a href="../../doc/wsdl_extensions/java_extension.html">here</a>.</p>
  +<p>The abstract functionality is tied to a java binding that describes how a java
class supports the abstract port type defined. This isn't a standard WSDL binding, instead
this binding is defined as a part of WSIF; you can find details on how to write a java binding
<a href="../../doc/wsdl_extensions/java_extension.html">here</a>.</p>
   <p>The <a href="AddressBook.wsdl">WSDL file</a> is in this sample directory.</p>
   <p><a href="client/dynamic/README.html">Here's</a> how to invoke this
service dynamically using WSIF's dynamic invocation interface (DII).</p>
   <p><a href="client/stub/README.html">Here's</a> how to invoke this service
by first generating the stub interface and using this directly through WSIF's dynamic proxy,
thus hiding all WSIF specifics from the client code. Note that the stub interface used is
the the service interface as defined by the JAX-RPC specification.</p>
  
  
  
  1.2       +1 -1      xml-axis-wsif/java/samples/simplesoap/client/dynamic/README.html
  
  Index: README.html
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/samples/simplesoap/client/dynamic/README.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- README.html	10 Dec 2002 11:03:26 -0000	1.1
  +++ README.html	11 Dec 2002 20:36:14 -0000	1.2
  @@ -21,6 +21,6 @@
     <li>JAR files required by Axis - log4j.jar, commons-logging.jar, commons-discovery.jar,
jaxrpc.jar, saaj.jar</li>
   </ul>
   </p>
  -<p>After you have set up the CLASSPATH in your environment, 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
samples.clients.DynamicInvoker file:/mywsifinstallation/samples/SimpleSOAP/StockquoteSOAP.wsdl
getQuote IBM</tt></p>
  +<p>After you have set up the CLASSPATH in your environment, 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
samples.clients.DynamicInvoker samples/simplesoap/StockquoteSOAP.wsdl getQuote IBM</tt></p>
   <hr width="100%">
   </body></html>
  
  
  
  1.2       +1 -1      xml-axis-wsif/java/samples/simplesoap/client/stub/README.html
  
  Index: README.html
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/samples/simplesoap/client/stub/README.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- README.html	10 Dec 2002 11:03:25 -0000	1.1
  +++ README.html	11 Dec 2002 20:36:14 -0000	1.2
  @@ -22,7 +22,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 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>
  +<tt>java samples.SimpleSOAP.client.static.Run 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>
  
  
  

Mime
View raw message