stevel      2002/10/17 16:39:16

  Modified:    java     release-notes.html
  Log:
  extended release notes
  
  Revision  Changes    Path
  1.15      +17 -12    xml-axis/java/release-notes.html
  
  Index: release-notes.html
  ===================================================================
  RCS file: /home/cvs/xml-axis/java/release-notes.html,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- release-notes.html        17 Oct 2002 23:14:08 -0000      1.14
  +++ release-notes.html        17 Oct 2002 23:39:16 -0000      1.15
  @@ -17,7 +17,12 @@
   <h2>Changes since Axis 1.0</h2>
   
   <ul>
  -<li>Fixed a bug where clients running java1.4 needed servlet.jar on their classpath
  +<li>Axis now includes a Castor serializer, handing off XML marshalling to
  +<a href="http://castor.exolab.org/";>Castor</a>. Castor integration offers schema
  +validation and autogenerated Java classes from a Schema. Pending documentation and 
tests,
  +this code is left for the experienced Castor user, who should look at the classes in
  +org.apache.axis.encoding.ser.castor to discover what is available.
  +<li>Fixed a bug where clients running Java1.4 needed servlet.jar on their classpath
   <li>Fixed
   <a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13682";> a bug</a>
   with Axis shutdown on Tomcat 3.3.1
  @@ -34,8 +39,8 @@
   Many users have requested a v1.0 so that they can work from a relatively
   stable base. Some users have even remained on Apache SOAP until v1.0 of
   Axis is available. Now Axis has surpassed Apache SOAP in function,
  -performance, and interoperability and, in particular, has passed Sun's 
  -JAX-RPC and SAAJ compliance tests, we decided to ship v1.0 as it 
  +performance, and interoperability and, in particular, has passed Sun's
  +JAX-RPC and SAAJ compliance tests, we decided to ship v1.0 as it
   currently stands.
   <p>
   However, this is far from the end of the road for Axis: there is more
  @@ -51,10 +56,10 @@
   </p>
   
   <h3>JAX-RPC</h3>
  -<p>This release is intended to be 100% compliant with the 
  -<a href="http://java.sun.com/xml/jaxrpc";>JAX-RPC</a> and 
  +<p>This release is intended to be 100% compliant with the
  +<a href="http://java.sun.com/xml/jaxrpc";>JAX-RPC</a> and
   <a href="http://java.sun.com/xml/saaj/";>SAAJ</a> specifications from Sun.
  -The Axis code has successfully passed the all of the JAX-RPC and SAAJ 
  +The Axis code has successfully passed the all of the JAX-RPC and SAAJ
   TCK (Technology Compatibility Kit) tests.</p>
   
   <h3>Why AXIS over SOAP 2.2?</h3>
  @@ -62,13 +67,13 @@
   <p>The Axis code has:</p>
   
   <ul>
  -  <li>Significantly higher performance than Apache SOAP 2.2 
  -  <li>Good interoperability with other SOAP implementations 
  -  <li>A streaming-oriented model for message parsing (SAX, not DOM) 
  -  <li>A modular, configurable message handling architecture 
  -  <li>A pluggable transport framework 
  +  <li>Significantly higher performance than Apache SOAP 2.2
  +  <li>Good interoperability with other SOAP implementations
  +  <li>A streaming-oriented model for message parsing (SAX, not DOM)
  +  <li>A modular, configurable message handling architecture
  +  <li>A pluggable transport framework
     <li>Support for WSDL generation and code generation from WSDL
  -  <li>An extensive package and functional test suite 
  +  <li>An extensive package and functional test suite
   </ul>
   
   <h3>What's New?</h3>
  
  
  


Reply via email to