You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by gd...@apache.org on 2003/01/13 17:26:30 UTC
cvs commit: xml-axis/java changelog.html TODO.txt release-notes.html
gdaniels 2003/01/13 08:26:29
Modified: java TODO.txt release-notes.html
Added: java changelog.html
Log:
Update TODO list a bit (remove old stuff, mostly)
Restructure release notes, factoring the change log out into a separate
file.
Revision Changes Path
1.80 +4 -62 xml-axis/java/TODO.txt
Index: TODO.txt
===================================================================
RCS file: /home/cvs/xml-axis/java/TODO.txt,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -r1.79 -r1.80
--- TODO.txt 3 Dec 2002 15:42:53 -0000 1.79
+++ TODO.txt 13 Jan 2003 16:26:29 -0000 1.80
@@ -8,43 +8,15 @@
* <Glen> Write TO DO list
+When you've completed a given item, please update the "changelog.html"
+file if appropriate.
+
! <team> Update the TO DO list to be current!
-1.0 MUST-DO
+1.1 MUST-DO
-----------
-! <> see bugzilla scrub below
-! <> fix javadocs
-! <> revamped documentation -- users shouldn't need to read the source code
-
-
-1.0 BUGZILLA SCRUB
-------------------
-Here is our initial scrub of bugzilla bugs for 1.0. We've come up with 6 categories:
-A - showstopper - don't release 1.0 without it
-B - planning for 1.0
-C - nice to have in 1.0
-D - post 1.0
-E - evaluation
-NR - not rated
-
-(note from Glen : Dims and I edited this down to JUST the "should do for 1.0" ones.
- This way bugzilla is the master source of info, and this list just tells us what's
- "todo" for 1.0 - although really a bugzilla search on things targeted for 1.0 should
- work too)
-
-7407 - B
-10355 - A
-10365 - B
-10479 - B
-10512 - B
-10944 - B - Glen
-11766 - If this is real, it looks like an "A". need to confirm.
-12167 - Glen will confirm
-12246 - Someone should confirm and fix for 1.0 if it's real
-12367 - Confirm, fix if real
-12572 - Glen will take a look (w/Rich)
MESSAGE PARSING / ENCODING
--------------------------
@@ -64,27 +36,6 @@
! <> Support <xsd:language> <xsd:ID>: <xsd:IDREF> <xsd:IDREFS> <xsd:ENTITY> <xsd:ENTITIES> <xsd:NOTATION>
! <> Support <xsd:restriction> facets correctly (do validation!)
-
-
-JAX-RPC COMPATIBILITY
----------------------
-! <Russell> NEVER name the SEI after the binding. Spec no longer allows it. Remember to change the user's guide, too.
-! <> Implement Service.getCalls() method. (maybe)
-! <> Implement generated Services' getCalls() method.
-! <> Implement Service.getHandlerRegistry() method.
-! <> Implement ServiceFactory.createService methods.
-! <> Implement TypeMapping and TypeMappingRegistry ala JAX-RPC 0.8
-! <> Implement Handler code ala JAX-RPC 0.8
-! <> Once we get word that javax.xml.rpc.namespace.NamespaceConstants is a real class (it's in the JAX-RPC javadocs but not in the spec) then use it.
-! <> Implement javax.xml.rpc.server interfaces.
-! <> Add some JAX-RPC compliance samples/tests.
-
-SAAJ COMPATIBILITY
-------------------
-! <> Implement javax.xml.soap interfaces (in message subsystem).
- (Not forgetting: SOAPBody.addFault/getFault/hasFault)
-! <> Obtain and pass a SAAJ TCK (Technology Compatibility Kit).
-
SOAP 1.2 SUPPORT
----------------
! <> Implement correct set of fault codes (4.4.5)
@@ -165,15 +116,6 @@
! <> Support generation of deploy.wsdd from Java2WSDL
! <> Support wildcards in stop object classes (i.e. "javax.*")
-
-X <Rich> Generate correct input/output elements for overloading.
-
-
-METHOD DISPATCH / SERVICE METADATA
-----------------------------------
-X <Glen> Use QName lookup when processing doc/lit style stuff with
- RPCProvider
-
GENERAL / UNCATEGORIZED
-----------------------
1.18 +9 -51 xml-axis/java/release-notes.html
Index: release-notes.html
===================================================================
RCS file: /home/cvs/xml-axis/java/release-notes.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- release-notes.html 3 Dec 2002 15:42:53 -0000 1.17
+++ release-notes.html 13 Jan 2003 16:26:29 -0000 1.18
@@ -21,8 +21,8 @@
<h3>About this release</h3>
<p>1.1 is primarily a bug fix release to deal with some problems which came to
- light after 1.0 went out. There are also some new features, see <a href="#whatsNew">What's
- New</a> for details. </p>
+ light after 1.0 went out. There are also some new features, see <a href="changelog.html">the
+ Axis change log</a> for details. </p>
<h3>Rationale for Releasing Axis 1.0</h3>
@@ -57,55 +57,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>Support for WSDL generation and code generation from WSDL
- <li>An extensive package and functional test suite
-</ul>
-
-<a name="whatsNew"><h3>What's New?</h3></a>
-<a name="changesSince1.0"><p>Changes since 1.0</p></a>
-<ul>
- <li>Axis supports JMS for reliable messaging between client and server. Note
- that the actual wire format of JMS messages is vendor-specific at present,
- so you may not be able to use this to connect arbitrary JMS clients and servers
- without special bridging software. Refer to your particular JMS vendor for
- details. (rule-of-thumb is "if you can get a JMS connection working,
- we can talk SOAP over it." :))
- <li>Many more WSDL and interop issues reported (thank you!) and fixed.
- <li>Axis ant tasks are now documented, and are much enhanced.
- <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
-</ul>
-<p>Changes since beta-3</p>
-<ul>
- <li>Axis now passes the JAX-RPC and SAAJ TCK test suites.
- <li>Many bugs have been fixed.
- <li>Axis now supports (almost) all XML Schema types in WSDL
- <li>Some basic performance tuning has been done
- <li>Attachments are now supported in WSDL2Java
-</ul>
-<p>Changes since beta-2:</p>
-<ul>
- <li>Support for the new version of the DIME spec
-</ul>
-<p>Changes since alpha-3:</p>
-<ul>
- <li>Closer to JAX-RPC compliance.</li>
- <li>Support for <A href="docs/user-guide.html#AttachmentsReference">SOAP Messages with Attachments</a>.</li>
- <li>Much better XML schema type support.</li>
- <li>Document/literal support.</li>
- <li>Now using the org.apache.commons.logging APIs as a common logging interface.</li>
- <li>Many minor bug fixes.</li>
+ <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
</ul>
<p>Please check out the included documentation and the <a href="http://xml.apache.org/axis/faq.html">FAQ</a> for more information.</a>
1.1 xml-axis/java/changelog.html
Index: changelog.html
===================================================================
<html>
<head>
<title>Axis Release Notes</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css">
<!--
.example { background:#ccccff }
.xml { background:#eeeeee }
body { font-family: Verdana, Arial, Helvetica, sans-serif; margin-left: 40px}
h2 { text-decoration: underline; background-color: #DCE1FF; background-position: left; margin-left: -30px}
h3 { margin-left: -10px}
h1 { margin-left: -30px}
-->
</style>
</head>
<body>
<h2>Axis Change Log</h2>
<h3>Changes from 1.0 to 1.1</h3>
<ul>
<li>Axis supports JMS for reliable messaging between client and server. Note
that the actual wire format of JMS messages is vendor-specific at present,
so you may not be able to use this to connect arbitrary JMS clients and servers
without special bridging software. Refer to your particular JMS vendor for
details. (rule-of-thumb is "if you can get a JMS connection working,
we can talk SOAP over it." :))
<li>Many more WSDL and interop issues reported (thank you!) and fixed.
<li>Axis ant tasks are now documented, and are much enhanced.
<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
</ul>
<h3>Changes from 1.0beta-3 to 1.0</h3>
<ul>
<li>Axis now passes the JAX-RPC and SAAJ TCK test suites.
<li>Many bugs have been fixed.
<li>Axis now supports (almost) all XML Schema types in WSDL
<li>Some basic performance tuning has been done
<li>Attachments are now supported in WSDL2Java
</ul>
<h3>Changes from 1.0beta-2 to 1.0beta-3</h3>
<ul>
<li>Support for the new version of the DIME spec
</ul>
<h3>Changes from 1.0alpha-3</h3>
<ul>
<li>Closer to JAX-RPC compliance.</li>
<li>Support for <A href="docs/user-guide.html#AttachmentsReference">SOAP Messages
with Attachments</a>.</li>
<li>Much better XML schema type support.</li>
<li>Document/literal support.</li>
<li>Now using the org.apache.commons.logging APIs as a common logging interface.</li>
<li>Many minor bug fixes.</li>
</ul>
</body>
</html>