axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From antel...@apache.org
Subject cvs commit: xml-axis-wsif/java readme.htm
Date Sat, 17 Aug 2002 09:34:11 GMT
antelder    2002/08/17 02:34:10

  Modified:    java     readme.htm
  Log:
  Created readme.htm for the target of the WSIF link off the AXIS home page.
  
  Revision  Changes    Path
  1.2       +25 -16    xml-axis-wsif/java/readme.htm
  
  Index: readme.htm
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/readme.htm,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- readme.htm	17 Aug 2002 09:17:52 -0000	1.1
  +++ readme.htm	17 Aug 2002 09:34:10 -0000	1.2
  @@ -1,24 +1,33 @@
   <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  -<meta name="GENERATOR" content="IBM WebSphere Studio Homepage Builder V6.0.0 for Windows">
  +<meta name="Author" content="Ant Elder">
   <meta http-equiv="Content-Style-Type" content="text/css"><title>Web Services
Invocation Framework for Java API - Overview</title>
   
   <link rel="stylesheet" href="README_files/wsif.txt" type="text/css"></head>
   
  -
   <body alink="#0000ff" bgcolor="#ffffff" leftmargin="2" topmargin="2" marginwidth="2"
marginheight="2">
   
   <h1><a name="WSIF Overview">WSIF: <br>
   Web Services Invocation Framework</a></h1>
   
  -The Web Service Invocation Framework (WSIF) is a simple Java API for invoking Web services,
no matter how or where the services are provided.  <BR>
  +The Web Services Invocation Framework (WSIF) is a simple Java API for invoking Web services,

  +no matter how or where the services are provided.<BR>
  +
   <BR>WSIF enables developers to interact with representations
  - of Web services instead of working directly with the Simple Object Access 
  - Protocol (SOAP) APIs, which is the usual programming model. With WSIF, developers
  - can work with the same programming model regardless of how the Web service is 
  - implemented and accessed. It frees the developer from the constraints of having to develop
services for particular transport protocols or service environments. Thus, it has an API that
provides binding-independent access to any Web service. <BR>
  -<BR>WSIF allows stubless or completely dynamic invocation of Web service, based upon
examination of the meta-data about the service at runtime. It also allows updated implementations
of a binding to be plugged into WSIF at runtime, and it allows the calling service to defer
choosing a binding until runtime. <BR>
  -<BR>Finally, WSIF is closely based upon WSDL,  so it can invoke any service that
can be described in WSDL. 
  +of Web services instead of working directly with the Simple Object Access 
  +Protocol (SOAP) APIs, which is the usual programming model. With WSIF, developers
  +can work with the same programming model regardless of how the Web service is 
  +implemented and accessed. It frees the developer from the constraints of having 
  +to develop services for particular transport protocols or service environments. 
  +Thus, it has an API that provides binding-independent access to any Web service.<BR>
  +
  +<BR>WSIF allows stubless or completely dynamic invocation of a Web service, based

  +upon examination of the meta-data about the service at runtime. It also allows 
  +updated implementations of a binding to be plugged into WSIF at runtime, and it 
  +allows the calling service to defer choosing a binding until runtime. <BR>
  +
  +<BR>Finally, WSIF is closely based upon WSDL,  so it can invoke any service 
  +that can be described in WSDL. 
   
   <H3>WSIF Structure</H3>
   
  @@ -33,9 +42,9 @@
   IIOP.<BR> 
   
   <BR>WSIF provides an API to allow the same client code to access any 
  -available binding, as the client code can then be written to the PortType
  -it can then be a deployment or configuration setting (or a code choice) 
  -which port and binding to use.<BR>
  +available binding. As the client code can then be written to the PortType
  +it can be a deployment or configuration setting (or a code choice) 
  +which port and binding it uses.<BR>
   <BR>
   WSIF uses 'providers' to support these multiple WSDL bindings. A provider 
   is a piece of code that supports a WSDL extension and allows invocation of 
  @@ -59,10 +68,10 @@
   	<li>J2EE.jar and JMS.jar from the <A href="http://java.sun.com/j2ee/">Java
J2EE site</A></li>
   	<li>Ant is required to build wsif. Ant is available at the <A href="http://jakarta.apache.org/ant">Apache
ANT website</A>.
   </li></ul>
  -<P>For now to successfully build WSIF all the prerequisites are required no mater

  -which providers are going to be used. It is the intention to change the build 
  -process so for example, the JMS.jar would only be required if JMS support is 
  -required in WSIF.
  +<P>Currently, in order to successfully build WSIF, all the above prerequisites 
  +are required no matter which providers are going to be used. However, it is the 
  +intention to change the build process so that, for example, the JMS.jar would 
  +only be required if JMS support is required in WSIF.
   </P>
   
   <h2><a name="sourcecode">Accessing Builds and Source Code</a></h2>
  
  
  

Mime
View raw message