aslom       2003/01/27 09:04:45

  Modified:    java/doc release_notes_2_0.html
  Log:
  updated 2.0 release notes with Jeremy email announcement draft as beginning, 
compressed recent chnages, added lsit of main features with hyperlinks to documentation
  
  Revision  Changes    Path
  1.2       +82 -61    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.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- release_notes_2_0.html    24 Jan 2003 14:42:58 -0000      1.1
  +++ release_notes_2_0.html    27 Jan 2003 17:04:45 -0000      1.2
  @@ -6,79 +6,100 @@
      <meta name="Author" content="Nirmal Mukhi, Owen Burroughs">
   </head>
   <body bgcolor="white">
  -<h2>Release Notes</h2>
  -<p>These are the release notes for Apache WSIF 2.0.</p>
  +<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. It has a pluggable architecture with protocol-specific 
"providers" to handle invocations according to a specific protocol.</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>Here is a list of *recent* changes to Apache WSIF (note that this is the first 
release, so this list of changes is not particularly illuminating).</p>
  -
  -
  -<H3>Changes to Apache WSIF</H3>
  +<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>
  +
  +<p>With WSIF, developers can work with the same programming model regardless
  +of how the Web service is implemented and accessed.</p>
  +
  +<p>WSIF  has a pluggable architecture with protocol-specific 
  +"providers" to handle invocations according to a specific protocol.
  +</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>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>
   
  +<H3>Main features:</H3>
   
   <ul>
  -<li>1/24/04: built RC4 release (tagged as <b>WSIF_2_0_RC4</b>)</li>
  -<li>1/23/04: built RC3 release (tagged as <b>WSIF_2_0_RC3</b>)</li>
  -
  -<li>added JCA sample
  +  <li>WSDL-centric: and works with abstract definition of service (portType) 
  +  hiding implementation details (protocol bindings and service location)</li>
  +  <li>pluggable: allows <a href="how_to_provider.html">new providers</a> to be 
  +  added that can be used by applications without code change to use new services 
  +  just by updating WSDL </li>
  +  <li>extensible: it is easy to experiment with new
  +  <a href="how_to_wsdl_extensions.html">extensions to WSDL</a></li>
  +  <li>flexible: allows for easy <a href="customising.html">customizations</a>
  +  <li>easy to integrate with JNDI to provide even greater transparency of where 
  +  are services located<li>multiple <a href="samples.html">samples</a> to 
  +  demonstrate use of WSIF to interact with services by SOAP, EJB, JMS, JCA and 
  +  local Java service providers<li>and many more ...</ul>
   
  -<li>fixed bugs:<br>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13646";>13646</a> 
WSIFOperation_ApacheAxis fails to set up Call's Parameter list<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15134";>15134</a>  AXIS 
provider requires mail.jar and acivation.jar even when not using attachements<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15578";>15578</a>  WSIF 
incorrectly handles returned attachment from service<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15691";>15691</a>  errors 
in docs<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15780";>15780</a>  WSIF 
stub invocation for doc style with unwrapped parts don't work<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15837";>15837</a>  
Attachments fail if in the wrong order<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16041";>16041</a>  There 
is no way to override the default (de)serializers used by the WSIF AXIS provider<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16196";>16196</a>  WSIF 
AXIS provider performance unacceptable<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16197";>16197</a>  axis 
provider messaging with attachments don't work<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16199";>16199</a>  
response soap headers not passed to WSIF client<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16199";>16199</a>  WSIF 
AXIS provider no longer supports jms:property parts in the input message<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16256";>16256</a>  WSIF 
AXIS Operation uses incorrect encoding style<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16271";>16271</a>  
WSIFUtils method initializeProviders should be public<BR>
  -<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16334";>16334</a>  WSIF 
NPE for a document style service which is not wrapped<BR>
  -
  -
  -<li>updated FAQ</li>
  -<li>added <a href="samples.html">DSL provider</a> sample to demonstrate how WSIF
  -can be used ot interact with many services each potentially implemented with
  -different protocol (EJB, JMS, SOAP, ...).</li>
  -<li>added <a href="samples.html">JMS</a> sample to demonstrate how WSIF
  -can be used to interacts with software accessible through the JMS API.</li>
  -
  -<li>12/20/02: built RC1 release (tagged as <b>WSIF_2_0_RC1</b>): new samples 
(<b>multibinding</b>,
  -<b>customfactory</b>),
  -misc. updates to documentation and samples</li>
  -
  -<li>built BETA1 release (tagged as <b>WSIF_2_0_BETA1</b>):
  -improvements to documentation that is now split in smaller pieces that
  -are better fitting into <a href="http://xml.apache.org/axis/wsif/";>
  -http://xml.apache.org/axis/wsif/</a> website<li>added EJB sample with documentation 
and pre-packaged jar
  -for deployment in JBoss&nbsp;
   
  -<li>built ALPHA2 release (tagged as <b>WSIF_2_0_ALPHA2</b>)
  +<H3>Recent Changes:</H3>
   
  -<li><b>changed release packaging</b>: there are now three different release builds:
   
   <ul>
  -<li><b>src</b>: only source file (no binaries) - essentially all that is needed
  -to compile WSIF if you downloaded all required jar files
  -<li><b>bin</b>: only binaries: just download few jar files that can not be 
distributed
  -and you are ready to run WSIF (no source code except for samples)
  -<li><b>all</b> = bin + src
  -</ul>
  -
  -<li>included samples to demonstrate invocation of SOAP service, local java and 
service with complex types and documentation for samples.
   
  +<li>new <a href="samples.html">samples</a>: added JCA sample, DSL provider
  +sample to demonstrate how WSIF
  +can be used to interact with many services each potentially implemented with
  +different protocol (EJB, JMS, SOAP, ...), added EJB sample with documentation and 
pre-packaged jar
  +for deployment in JBoss, added JMS sample to demonstrate how WSIF
  +can be used to interacts with software accessible through the JMS API, added 
  +multi binding and custom factory samples to demonstrate flexibility of WSIF 
  +(custom factory currently does not work depending on future changes in WSIF)</li>
   
  -<li><b>documentation changes</b>
  +<li>improved documentation:
   factored out <a href="../readme.htm1">readme.htm1</a> into smaller pieces that are 
put in doc/ (like cvs and requirements)
   updated doc/ with factored out info about cvs and requirements and improved build 
instructions,
   moved wsdl_extensions to doc/ from README_files,
  -simplified wsif.css (much less colors, easier to read ...)
  +simplified wsif.css (much less colors, easier to read ...), added
  +<a href="faq.html">FAQ</a><li>fixed bugs:
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13646";>13646</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15134";>15134</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15578";>15578</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15691";>15691</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15780";>15780</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15837";>15837</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16041";>16041</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16196";>16196</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16197";>16197</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16199";>16199</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16199";>16199</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16256";>16256</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16271";>16271</a>
  +<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16334";>16334</a>
  +
  +
  +<li>changed release packaging: there are now three different release builds: 
  +<b>src</b>: only source file (no binaries) - essentially all that is needed
  +to compile WSIF if you downloaded all required jar files, 
  +<b>bin</b>: only binaries: just download few jar files that can not be distributed
  +and you are ready to run WSIF (no source code except for samples), 
  +<b>all</b> = bin + src
  +
  +<li><b>documentation changes</b>
   
   <li>preparing first official release: added <a href="RELEASE_TASKS.txt">
   RELEASE_TASKS.txt</a><li>work on first alpha release
  @@ -96,4 +117,4 @@
   <a href="http://www.extreme.indiana.edu/~aslom/";>Aleksander Slominski</a>
   <br>Last modified: $Id$</address>
   </body>
  -</html>
  +</html>
  \ No newline at end of file
  
  
  


Reply via email to