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/04/15 18:46:51 UTC
cvs commit: xml-axis/java/docs reference.html
gdaniels 2003/04/15 09:46:50
Modified: java release-notes.html
java/docs reference.html
Log:
Some updates in preparation for releasing 1.1
Revision Changes Path
1.21 +24 -52 xml-axis/java/release-notes.html
Index: release-notes.html
===================================================================
RCS file: /home/cvs/xml-axis/java/release-notes.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- release-notes.html 4 Mar 2003 04:35:24 -0000 1.20
+++ release-notes.html 15 Apr 2003 16:46:50 -0000 1.21
@@ -14,63 +14,35 @@
</style>
</head>
<body>
-<h2>Axis 1.1 RC2 Release Notes</h2>
+<h2>Axis 1.1 Release Notes</h2>
-<p>This is the <a href="http://xml.apache.org/axis/releases.html">1.1 RC2 release</a>
+<p>This is the <a href="http://xml.apache.org/axis/releases.html">1.1 release</a>
of the <a href="http://xml.apache.org/axis"> Axis SOAP library</a>.</p>
<h3>About this release</h3>
-<p>1.1 RC2 is being released to get ready to release 1.1 in March. This release
- serves to get recent bugfixes and improvements out into the testing community
- so that 1.1 final can be as good as possible. Please bang on the APIs, kick
- the tires, and let us know about any problems you have!</p>
-<hr>
-<em>(the following are older release notes which will be moved for the final 1.1
-release)</em>
-<h3>Rationale for Releasing Axis 1.0</h3>
-
-
-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
-currently stands.
-<p>
-However, this is far from the end of the road for Axis: there is more
-documentation to be written; the SOAP v1.2 spec. needs to be tracked to
-completion and implemented fully; major functional enhancements and
-architectural improvements are being considered. We particularly encourage
-you to submit improvements to the documentation, however large or small and
-in any format, to axis-dev@xml.apache.org. Also, interoperability
-is always a concern, so please report all <i>replicatable</i> bugs.</p>
-
-<p>
-The Axis Development Team
-</p>
-
+<p>This is Axis 1.1. <em><TBD></em></p>
+<h3>Changes From 1.0 to 1.1</h3>
+<p><em><TBD></em></p>
+<p>However, this is far from the end of the road for Axis: there is more documentation
+ to be written, and major functional enhancements and architectural improvements
+ are being considered.</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
-<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
-TCK (Technology Compatibility Kit) tests.</p>
-
-<h3>Why AXIS over SOAP 2.2?</h3>
-
-<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>
-
-<p>Please check out the included documentation and the <a href="http://xml.apache.org/axis/faq.html">FAQ</a> for more information.</a>
+<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 TCK (Technology
+ Compatibility Kit) tests.</p>
+<h3>More Info</h3>
+
+<p>Please check out the included documentation and the <a href="http://xml.apache.org/axis/faq.html">FAQ</a>
+ for more information.</p>
+<h3>How You Can Help</h3>
+<p>We particularly encourage you to submit improvements to the documentation,
+ however large or small and in any format, to axis-dev@xml.apache.org. Also,
+ interoperability is always a concern, so please report all <i>replicable</i>
+ bugs.</p>
+<p>Thanks for trying Axis!</p>
+<p>-- The Axis Development Team</p>
+<p> </p>
</body>
</html>
1.25 +98 -109 xml-axis/java/docs/reference.html
Index: reference.html
===================================================================
RCS file: /home/cvs/xml-axis/java/docs/reference.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- reference.html 28 Mar 2003 07:34:35 -0000 1.24
+++ reference.html 15 Apr 2003 16:46:50 -0000 1.25
@@ -574,97 +574,84 @@
</globalConfiguration>
</pre>
<table>
-
-<tr><td><b>adminPassword</b></td>
-<td>Adminstrator password, as used by AdminService.
-</td>
-</tr>
-
-<tr><td><b>attachments.Directory</b></td>
-<td>The directory where attachments end up. This should be in the syntax
-appropriate for the target platform.
-</td>
-</tr>
-
-<tr><td><b>attachments.implementation</b></td>
-<td>
-Name of class that implements attachments support. Default is
-<tt>org.apache.axis.attachments.AttachmentsImpl</tt>
-</td>
-</tr>
-
-<tr><td><b>axis.enableListQuery</b></td>
-<td>Flag to enable the "list the WSDD" feature. Set to false by default,
-because listing the current system config can expose information (such as the
-adminservice password) that one does not want widely avaialable.
-</td>
-</tr>
-
-<tr><td><b>axis.Compiler</b></td>
-<td>Compiler adapter classname for JWS compilation. Default is
-<tt>org.apache.axis.components.compiler.Javac</tt>; change this to
-<tt>org.apache.axis.components.compiler.Jikes</tt> to invoke jikes instead.
-</td>
-</tr>
-
-<tr><td><b>axis.development.system</b></td>
-<td>Flag to switch the system from <i>production</i> (false) to
-<i>development</i> (true). A development system gives out stack traces
-and other information that production boxes should not.
-</td>
-
-<tr><td><b>axis.engineConfigClass</b></td>
-<td>Name of a class that provides Axis configuration. Implement a new
-class implementing <tt>EngineConfiguration</tt> and name it here to
-use alternate configuration mechanisms.
-</td>
-
-<tr><td><b>axis.jws.servletClassDir</b></td>
-<td>Path to where compiled JWS pages are placed.
-</td>
-</tr>
-
-<tr><td><b>axis.sendMinimizedElements</b></td>
-<td>Flag to turn on support for a when .NET1.0 can't
-correctly handle some bits of XML
-<a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17021">
-that it should.
-</a> The flag defaults to true;
-if some .NET clients are failing to handle a Web Service returning an
-empty array inside another object, set this flag to <i>false</i>.
-</td>
-</tr>
-
-<tr><td><b>enable2DArrayEncoding</b></td>
-<td>Set this to "true" to turn 2D array encoding on;
- this encoding is incompatible with .NET 1.0: default="false".
-</td>
-</tr>
-
-
-<tr><td><b>sendMultiRefs</b></td>
-<td>true/false flag to control whether multirefs are sent or not.
-</td>
-</tr>
-
-<tr><td><b>sendXMLDeclaration</b></td>
-<td>true/false flag to control whether the <?xml?> declaration is sent in messages
-</td>
-</tr>
-
-<tr><td><b>sendXsiTypes</b></td>
-<td>true/false flag to enable/disable sending the type of every value sent over the wire.
-Defaults to true.
-</td>
-</tr>
-
-<tr><td><b>use-servlet-security</b></td>
-<td>Set this flag to hand authentication off to the servlet container.
-</td>
-</tr>
-
-
-<!-- end table -->
+ <tr>
+ <td><b>adminPassword</b></td>
+ <td>Adminstrator password, as used by AdminService. </td>
+ </tr>
+ <tr>
+ <td><b>attachments.Directory</b></td>
+ <td>The directory where attachments end up. This should be in the syntax appropriate
+ for the target platform. </td>
+ </tr>
+ <tr>
+ <td><b>attachments.implementation</b></td>
+ <td> Name of class that implements attachments support. Default is <tt>org.apache.axis.attachments.AttachmentsImpl</tt>
+ </td>
+ </tr>
+ <tr>
+ <td><b>axis.enableListQuery</b></td>
+ <td>Flag to enable the "list the WSDD" feature. Set to false by default, because
+ listing the current system config can expose information (such as the adminservice
+ password) that one does not want widely avaialable. </td>
+ </tr>
+ <tr>
+ <td><b>axis.Compiler</b></td>
+ <td>Compiler adapter classname for JWS compilation. Default is <tt>org.apache.axis.components.compiler.Javac</tt>;
+ change this to <tt>org.apache.axis.components.compiler.Jikes</tt> to invoke
+ jikes instead. </td>
+ </tr>
+ <tr>
+ <td><b>axis.development.system</b></td>
+ <td>Flag to switch the system from <i>production</i> (false) to <i>development</i>
+ (true). A development system gives out stack traces and other information
+ that production boxes should not. </td>
+ <tr>
+ <td><b>axis.engineConfigClass</b></td>
+ <td>Name of a class that provides Axis configuration. Implement a new class
+ implementing <tt>EngineConfiguration</tt> and name it here to use alternate
+ configuration mechanisms. </td>
+ <tr>
+ <td><b>axis.jws.servletClassDir</b></td>
+ <td>Path to where compiled JWS pages are placed. </td>
+ </tr>
+ <tr>
+ <td><b>axis.sendMinimizedElements</b></td>
+ <td>Flag to turn on support for a when .NET1.0 can't correctly handle some
+ bits of XML <a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17021">
+ that it should. </a> The flag defaults to true; if some .NET clients are
+ failing to handle a Web Service returning an empty array inside another
+ object, set this flag to <i>false</i>. </td>
+ </tr>
+ <tr>
+ <td><b>enable2DArrayEncoding</b></td>
+ <td>Set this to "true" to turn 2D array encoding on; this encoding is incompatible
+ with .NET 1.0: default="false". </td>
+ </tr>
+ <tr>
+ <td><b>sendMultiRefs</b></td>
+ <td>true/false flag to control whether multirefs are sent or not. </td>
+ </tr>
+ <tr>
+ <td><b>sendXMLDeclaration</b></td>
+ <td>true/false flag to control whether the <?xml?> declaration is sent
+ in messages </td>
+ </tr>
+ <tr>
+ <td><b>sendXsiTypes</b></td>
+ <td>true/false flag to enable/disable sending the type of every value sent
+ over the wire. Defaults to true. </td>
+ </tr>
+ <tr>
+ <td><strong>SingleSOAPVersion</strong></td>
+ <td>When set to either "1.1" or "1.2", this configures
+ the engine to only accept the specified SOAP version. Attempts to connect
+ to the engine using another version will result in a fault.</td>
+ </tr>
+ <tr>
+ <td><b>use-servlet-security</b></td>
+ <td>Set this flag to hand authentication off to the servlet container. </td>
+ </tr>
+ <!-- end table -->
</table>
<a name="individual_service" />
@@ -681,24 +668,26 @@
More may exist.
<table>
-
-<tr><td><b>style</b></td>
-<td>whether to use RPC:enc or doc/lit encoding
-</td>
-</tr>
-
-<tr><td><b>wsdlFile</b></td>
-<td>The path to a WSDL File; can be an absolute path or
-a resource that axis.jar can load. Useful to export
-your custom WSDL file. When specify a path to a resource, place a forward
-slash to start at the beginning of the classpath (e.g
-"/org/someone/res/mywsdl.wsdl"). How does Axis know whether to return
-a file or resource? It looks for a file first, if that is missing a
-resource is returned.
-
-</td>
-</tr>
-<!-- TODO: what does this mean?
+ <tr>
+ <td><b>style</b></td>
+ <td>whether to use RPC:enc or doc/lit encoding </td>
+ </tr>
+ <tr>
+ <td><strong>SingleSOAPVersion</strong></td>
+ <td>When set to either "1.1" or "1.2", this configures
+ a service to only accept the specified SOAP version. Attempts to connect
+ to the service using another version will result in a fault.</td>
+ </tr>
+ <tr>
+ <td><b>wsdlFile</b></td>
+ <td>The path to a WSDL File; can be an absolute path or a resource that axis.jar
+ can load. Useful to export your custom WSDL file. When specify a path to
+ a resource, place a forward slash to start at the beginning of the classpath
+ (e.g "/org/someone/res/mywsdl.wsdl"). How does Axis know whether to return
+ a file or resource? It looks for a file first, if that is missing a resource
+ is returned. </td>
+ </tr>
+ <!-- TODO: what does this mean?
<tr><td><b>streaming</b></td>
<td>
</td>