hughesj     2003/01/27 09:18:03

  Modified:    java/doc release_notes_2_0.html
  Log:
  Small updates to announcement section
  
  Revision  Changes    Path
  1.3       +28 -24    xml-axis-wsif/java/doc/release_notes_2_0.html
  
  Index: release_notes_2_0.html
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/doc/release_notes_2_0.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- release_notes_2_0.html    27 Jan 2003 17:04:45 -0000      1.2
  +++ release_notes_2_0.html    27 Jan 2003 17:18:03 -0000      1.3
  @@ -8,36 +8,40 @@
   <body bgcolor="white">
   <h2>Release Notes for Apache WSIF 2.0</h2>
   
  -<p>WSIF (the "Web Services Invocation Framework") is a 
  -WSDL-based API for invoking WSDL-described services. 
  -WSIF developers interact with Web Services
  -at the abstract level through their WSDL descriptions, independently of
  -APIs used to communicate in specific a message format and over a specific
  -network protocol (eg SOAP APIs).
  +<p> WSIF (the "Web Services Invocation Framework") is a WSDL-based API for
  +    invoking WSDL-described services. WSIF developers interact with Web Services
  +    at the abstract level through their WSDL descriptions. This is done
  +    independently of APIs specific to a message format or network protocol
  +    (eg SOAP APIs).
   </p>
   
  -<p>With WSIF, developers can work with the same programming model regardless
  -of how the Web service is implemented and accessed.</p>
  +<p> With WSIF, developers work with the same programming model regardless of
  +    how the Web service is implemented and accessed. WSIF achieves this with a
  +    pluggable architecture with protocol-specific "providers" to handle
  +    invocations according to a specific protocol.
  +</p>
   
  -<p>WSIF  has a pluggable architecture with protocol-specific 
  -"providers" to handle invocations according to a specific protocol.
  +<p> Apache WSIF 2.0 comes bundled with providers for SOAP (using Apache SOAP or
  +    Axis), local java classes, EJBs, JMS services and applications accessible
  +    via Java Connectors. WSIF also describes the specific WSDL extensions used
  +    to make these kinds of applications accessible as WSDL-described services.
   </p>
   
  -<p>Apache WSIF 2.0 comes bundled with providers for SOAP 
  -(using Apache SOAP or Axis), local java classes, EJBs, 
  -JMS services and applications accessible via Java Connectors. 
  -WSIF also describes the specific WSDL extensions used 
  -to make these kinds of applications accessible as WSDL-described services.</p>
  +<p> 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.
  +</p>
   
  -<p>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.
  +<p> This is the first release of WSIF since it was contributed to the ASF, and
  +    is named 2.0 to avoid confusion with previous non-Apache licensed 1.x
  +    versions.
   </p>
   
  -<p>This is the first release of WSIF since it was contributed to the ASF by IBM, 
  -and is named 2.0 to avoid confusion with previous non-Apache licensed 1.x
  -versions.</p>
  +<p> Thanks to all the committers, contributors and usersfor their efforts in
  +    helping get our first release out.
  +</p>
   
   <H3>Main features:</H3>
   
  @@ -117,4 +121,4 @@
   <a href="http://www.extreme.indiana.edu/~aslom/";>Aleksander Slominski</a>
   <br>Last modified: $Id$</address>
   </body>
  -</html>
  \ No newline at end of file
  +</html>
  
  
  


Reply via email to