axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rkell...@apache.org
Subject cvs commit: xml-axis/java/docs reference.html integration-guide.html index.html developers-guide.html AxisTestRedesign.html
Date Fri, 11 Jul 2003 23:56:43 GMT
rkellogg    2003/07/11 16:56:43

  Modified:    java/docs reference.html integration-guide.html index.html
                        developers-guide.html AxisTestRedesign.html
  Log:
  Updated all references to "AXIS" with "Axis" for consistency.
  
  Revision  Changes    Path
  1.26      +2 -2      xml-axis/java/docs/reference.html
  
  Index: reference.html
  ===================================================================
  RCS file: /home/cvs/xml-axis/java/docs/reference.html,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- reference.html	15 Apr 2003 16:46:50 -0000	1.25
  +++ reference.html	11 Jul 2003 23:56:42 -0000	1.26
  @@ -188,7 +188,7 @@
   The root directory for all emitted files. 
   <h4> -d, --deployScope &lt;argument></h4>
   Add scope to deploy.wsdd: "Application", "Request", or "Session".&nbsp; If this 
  -option does not appear, no scope tag appears in deploy.wsdd, which the AXIS runtime 
  +option does not appear, no scope tag appears in deploy.wsdd, which the Axis runtime 
   defaults to "Request". 
   <h4> -t, --testCase</h4>
   Generate a client-side JUnit test case.&nbsp; This test case can stand on its 
  @@ -750,7 +750,7 @@
     <td valign=top><tt>org.apache.axis.enterprise</tt></td>
     <td>''Enterprise'' level stuff, which generally means  
     stuff that an enterprise product might want to track, but in a 
  -  simple environment (like the AXIS build) would be nothing more than a nuisance.
  +  simple environment (like the Axis build) would be nothing more than a nuisance.
     
   </tr>
   </table>
  
  
  
  1.21      +45 -45    xml-axis/java/docs/integration-guide.html
  
  Index: integration-guide.html
  ===================================================================
  RCS file: /home/cvs/xml-axis/java/docs/integration-guide.html,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- integration-guide.html	6 Apr 2003 09:04:09 -0000	1.20
  +++ integration-guide.html	11 Jul 2003 23:56:42 -0000	1.21
  @@ -33,8 +33,8 @@
   <h2>
   <a NAME="Introduction"></a>Introduction</h2>
   The primary purpose of this guide is
  -to present how AXIS can be integrated into an existing web application
  -server, such as Tomcat or WebSphere, for example.&nbsp; AXIS has a number
  +to present how Axis can be integrated into an existing web application
  +server, such as Tomcat or WebSphere, for example.&nbsp; Axis has a number
   of Pluggable APIs that are necessary for such an integration.
   <p>
   The reader may find useful background information in the
  @@ -42,7 +42,7 @@
   
   <h2>
   <a NAME="Pluggable APIs"></a>Pluggable APIs</h2>
  -The following are the points that are pluggable in order to integrate AXIS
  +The following are the points that are pluggable in order to integrate Axis
   into a web application server.
   The first subsection details a number of pluggable components in general.
   More details are provided for other components in the remaining
  @@ -51,7 +51,7 @@
   <h3>
   <a NAME="Components"></a>Components</h3>
   This section describes in general how to plug specializations
  -of various components into AXIS.
  +of various components into Axis.
   
   <h4>
   General Strategy
  @@ -60,7 +60,7 @@
   <ul>
   <li>Develop implementation of components interface</li>
   <br>&nbsp;
  -<li>Define the implementation class to AXIS by either creating
  +<li>Define the implementation class to Axis by either creating
   a service definition file (prefered)
   or by setting a system property.
   <ul>
  @@ -111,7 +111,7 @@
   <code>org.apache.axis.components.compiler.Jikes</code></li>
   <br>&nbsp;
   <li>Since <code>org.apache.axis.components.compiler.Jikes</code>
  -is packaged with AXIS, all that needs to be done is to ensure
  +is packaged with Axis, all that needs to be done is to ensure
   that the service definition file is loadable by a class loader.
   </li>
   </ul>
  @@ -196,7 +196,7 @@
   <!--
   <h3>
   <a NAME="System Management Plug"></a>System Management</h3>
  -What points are necessary to manage AXIS?
  +What points are necessary to manage Axis?
   <ul>
   <li>
   Justification/Rationale - why is this plug point necessary?&nbsp; Spec
  @@ -232,7 +232,7 @@
   -->
   
   <h3><a NAME="Logging/Tracing Plug"></a>Logging/Tracing</h3>
  -AXIS logging and tracing is based on the Logging component of the
  +Axis logging and tracing is based on the Logging component of the
   <a href="http://jakarta.apache.org/commons/index.html">Jakarta Commons</a>
   project, or the Jakarta Commons Logging (JCL) SPI.
   The JCL provides a Log interface with thin-wrapper implementations for
  @@ -245,7 +245,7 @@
   
   <h4>Justification/Rationale</h4>
   A pluggable logging/trace facility enables
  -AXIS to direct logging/trace messages to a host web application server's
  +Axis to direct logging/trace messages to a host web application server's
   logging facility.
   A central logging facility with a single point of configuration/control
   is superior to distinct logging mechanisms for each of a multitude of
  @@ -357,9 +357,9 @@
   
   <h3>
   <a NAME="Configuration Plug"></a>Configuration</h3>
  -<br>The internal data model used by AXIS is based on
  -an AXIS specific data model: Web Services Deployment Descriptor (WSDD).
  -AXIS initially obtains the WSDD information for a
  +<br>The internal data model used by Axis is based on
  +an Axis specific data model: Web Services Deployment Descriptor (WSDD).
  +Axis initially obtains the WSDD information for a
   service from an instance of <code>org.apache.axis.EngineConfiguration</code>.
   
   <p>The EngineConfiguration is provided by an implementation of
  @@ -374,17 +374,17 @@
   <li>
   Justification/Rationale</li>
   <br>While the default behaviour is sufficient for general use of
  -AXIS, integrating AXIS into an existing application server may
  +Axis, integrating Axis into an existing application server may
   require an alternate deployment model.
   A customized implementation of the EngineConfigurationFactory
  -would map from the hosts deployment model to AXIS's internal
  +would map from the hosts deployment model to Axis's internal
   deployment model.
   <br>&nbsp;
   
   <li>
   Mechanism</li>
   <br>The relevant sequence of instructions used to obtain
  -configuration information and initialize AXIS is as follows:
  +configuration information and initialize Axis is as follows:
   <ul>
   <br>
   <code>EngineConfigurationFactory factory = EngineConfigurationFactoryFinder(someContext);</code>
  @@ -396,7 +396,7 @@
   <br>The details may vary (server versus client, whether other factories are involved,
etc).
   Regardless, the point is that integration code is responsible for
   calling <code>EngineConfigurationFactoryFinder(someContext)</code>
  -and ensuring that the results are handed to AXIS.&nbsp;
  +and ensuring that the results are handed to Axis.&nbsp;
   <code>someContext</code> is key to how the factory finder
   locates the appropariate implementation of
   EngineConfigurationFactory to be used, if any.
  @@ -533,11 +533,11 @@
   
   <h3>
   <a NAME="Internationalization Plug"></a>Internationalization</h3>
  -AXIS supports internationalization by providing
  -both a property file of the strings used in AXIS,
  +Axis supports internationalization by providing
  +both a property file of the strings used in Axis,
   and an extension mechanism that facilitates
  -accessing internal AXIS messages and extending the messages
  -available to integration code based on existing AXIS code.
  +accessing internal Axis messages and extending the messages
  +available to integration code based on existing Axis code.
   
   <h4>
   <a NAME="Translation"></a>Translation</h4>
  @@ -548,9 +548,9 @@
   
   <br>
   In order for readers of languages other than English
  -to be comfortable with AXIS,
  -we provide a mechanism for the strings used in AXIS to be translated.
  -We do not provide any translations in AXIS;
  +to be comfortable with Axis,
  +we provide a mechanism for the strings used in Axis to be translated.
  +We do not provide any translations in Axis;
   we merely provide a means by which translators
   can easily plug in their translations.
   <br>&nbsp;
  @@ -558,13 +558,13 @@
   <li>
   Mechanism</li>
   <br>
  -AXIS provides english messages in the
  +Axis provides english messages in the
   Java resource named
   org.apache.axis.i18n.resource.properties
   (in the source tree, the file is named
   xml-axis/java/src/org/apache/axis/i18n/resource.properties).
   
  -<p>AXIS makes use of the Java internationalization mechanism -
  +<p>Axis makes use of the Java internationalization mechanism -
   i.e., a java.util.ResourceBundle backed by a properties file -
   and the java.text.MessageFormat class to substitute
   parameters into the message text.
  @@ -592,13 +592,13 @@
   <p>For example: <code>myMsg00=My {0} is {1}.</code>
   
   <p>Translation requires creating an
  -alternate version of the property file provided by AXIS
  +alternate version of the property file provided by Axis
   for a target language.
   The JavaDoc for <code>java.utils.ResourceBundle</code>
   provides details on how to identify different property
   files for different locales.
   
  -<p>For details on using AXIS's internationalization tools,
  +<p>For details on using Axis's internationalization tools,
   see the <a href="developers-guide.html">Developer's Guide</a>.
   <br>&nbsp;
   
  @@ -608,26 +608,26 @@
   <br>The default behavior, meaning what happens when a translated file doesn't
   exist for a given locale, is to fall back on the English-language properties
   file.&nbsp; If that file doesn't exist (unlikely unless something is seriously
  -wrong), AXIS will throw an exception with an English-language reason message.
  +wrong), Axis will throw an exception with an English-language reason message.
   <br>&nbsp;
   </ul>
   
   <h4>
   <a NAME="Extending Message Files"></a>Extending Message Files</h4>
  -AXIS provides a Message file extension mechanism
  -that allows AXIS-based code to use AXIS message keys,
  +Axis provides a Message file extension mechanism
  +that allows Axis-based code to use Axis message keys,
   as well as new message keys unique to the extended code.
   
   <ul>
   <li>
   Justification/Rationale</li>
   <br>
  -AXIS provides pluggable interfaces for
  -various AXIS entities, including EngineConfigurationFactory's,
  +Axis provides pluggable interfaces for
  +various Axis entities, including EngineConfigurationFactory's,
   Provides, and Handlers.
  -AXIS also provides a variety of implementations
  +Axis also provides a variety of implementations
   of these entities.
  -It is convenient to use AXIS source code for
  +It is convenient to use Axis source code for
   such implementations as starting points for developing
   extentions and customizations that fulfill the unique needs
   of the end user.
  @@ -635,10 +635,10 @@
   
   <li>
   Procedure</li>
  -<br>To extend the AXIS message file:
  +<br>To extend the Axis message file:
   <br>&nbsp;
   <ul>
  -<li>Copy the AXIS source file
  +<li>Copy the Axis source file
   <code>java/src/org/apache/axis/i18n/Messages.java</code>
   to your project/package, say
   <code>my/project/package/path/Messages.java</code>.
  @@ -660,7 +660,7 @@
   Add new message key/value pairs to this file.
   </li>
   <br>&nbsp;
  -<li>As you copy AXIS source files over to your project,
  +<li>As you copy Axis source files over to your project,
   change the <code>import org.apache.axis.i18n.Messages</code>
   statement to <code>import my.project.package.path.Messages</code>.
   </li>
  @@ -701,7 +701,7 @@
   <code>Messages</code> class copied to your extensions directory.
   <p>Unless changed, the default behavior, meaning what happens when a key
   isn't defined in the new properties file,
  -is to fall back to the AXIS properties file
  +is to fall back to the Axis properties file
   (org.apache.axis.i18n.resource.properties).
   <br>&nbsp;
   </ul>
  @@ -709,7 +709,7 @@
   
   <h3>
   <a NAME="Performance Monitoring Plug"></a>Performance Monitoring</h3>
  -AXIS does not yet include specific Performance Monitoring Plugs.
  +Axis does not yet include specific Performance Monitoring Plugs.
   <!--
   <ul>
   <li>
  @@ -747,7 +747,7 @@
   
   <h3>
   <a NAME="Encoding Plug"></a>Encoding</h3>
  -AXIS does not yet include an Encoding Plug.
  +Axis does not yet include an Encoding Plug.
   <!--
   How can a system integrator plug in other encoding mechanisms such as SOAP
   1.2 or optimized XML-based encoding?
  @@ -787,13 +787,13 @@
   
   <h3>
   <a NAME="WSDL plug"></a>WSDL Parser and Code Generator Framework</h3>
  -WSDL2Java is AXIS's tool to generate Java artifacts from WSDL.&nbsp; This
  -tool is extensible.&nbsp; If users of AXIS wish to extend AXIS, then they
  +WSDL2Java is Axis's tool to generate Java artifacts from WSDL.&nbsp; This
  +tool is extensible.&nbsp; If users of Axis wish to extend Axis, then they
   may also need to extend or change the generated artifacts.&nbsp; For example,
  -if AXIS is inserted into some product which has an existing deployment
  -model that's different than AXIS's deployment model, then that product's
  +if Axis is inserted into some product which has an existing deployment
  +model that's different than Axis's deployment model, then that product's
   version of WSDL2Java will be required to generate deployment descriptors
  -other than AXIS's deploy.wsdd.
  +other than Axis's deploy.wsdd.
   <p>What follows immediately is a description of the framework.&nbsp; If
   you would rather dive down into the dirt of <a href="#WSDL Examples">examples</a>,
   you could learn a good deal just from them.&nbsp; Then you could come back
  
  
  
  1.14      +2 -2      xml-axis/java/docs/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /home/cvs/xml-axis/java/docs/index.html,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- index.html	8 Jun 2003 01:48:38 -0000	1.13
  +++ index.html	11 Jul 2003 23:56:42 -0000	1.14
  @@ -47,13 +47,13 @@
   <li>
   <a href="apiDocs/index.html">API Documentation</a></li>
   <li>
  -<a href="building-axis.html">Building Axis</a> - Guidelines for building AXIS
  +<a href="building-axis.html">Building Axis</a> - Guidelines for building Axis
   with/without optional components.</li>
   
   
   <li>
   <a href="developers-guide.html">Developer's Guide</a> - Collection of guidelines
  -for developing code in AXIS.</li>
  +for developing code in Axis.</li>
   
   <li>
   <a href="integration-guide.html">Integration Guide</a> - Description of
  
  
  
  1.36      +37 -37    xml-axis/java/docs/developers-guide.html
  
  Index: developers-guide.html
  ===================================================================
  RCS file: /home/cvs/xml-axis/java/docs/developers-guide.html,v
  retrieving revision 1.35
  retrieving revision 1.36
  diff -u -r1.35 -r1.36
  --- developers-guide.html	8 Jun 2003 01:48:38 -0000	1.35
  +++ developers-guide.html	11 Jul 2003 23:56:42 -0000	1.36
  @@ -125,15 +125,15 @@
   <p>
   The <code>org.apache.axis.components.image</code> package demonstrates
   both a factory, and supporting classes for different image tools used
  -by AXIS.  This is representative of a pluggable component that uses
  -external tooling, isolating it behind a 'thin' wrapper to AXIS that
  -provides only a limited interface to meet AXIS minimal requirements.
  +by Axis.  This is representative of a pluggable component that uses
  +external tooling, isolating it behind a 'thin' wrapper to Axis that
  +provides only a limited interface to meet Axis minimal requirements.
   This allows future designers
  -and implementors to gain an explicit understanding of the AXIS's
  +and implementors to gain an explicit understanding of the Axis's
   specific requirements on these tools.
   <h3>
   <a NAME="Logging/Tracing"></a>Logging/Tracing</h3>
  -AXIS logging and tracing is based on the Logging component of the
  +Axis logging and tracing is based on the Logging component of the
   <a href="http://jakarta.apache.org/commons/index.html">Jakarta Commons</a>
   project, or the Jakarta Commons Logging (JCL) SPI.
   The JCL provides a Log interface with thin-wrapper implementations for
  @@ -214,7 +214,7 @@
   appropriate in content and severity.
   The following guidelines are suggested:
   <ul>
  -<li>fatal - Severe errors that cause the AXIS server to terminate prematurely.
  +<li>fatal - Severe errors that cause the Axis server to terminate prematurely.
   Expect these to be immediately visible on a console,
   and MUST be internationalized.</li>
   <br>&nbsp;
  @@ -247,17 +247,17 @@
   The Jakarta Commons Logging (JCL) SPI
   can be configured to use different logging toolkits.
   To configure which logger is used by the JCL, see the
  -<a href="integration-guide.html">AXIS System Integration Guide</a>.
  +<a href="integration-guide.html">Axis System Integration Guide</a>.
   <p>
   Configuration of the behavior of the JCL ultimately depends upon the
   logging toolkit being used.
  -The JCL SPI (and hence AXIS) uses
  +The JCL SPI (and hence Axis) uses
   <a href="http://jakarta.apache.org/log4j/docs/index.html">Log4J</a>
   by default if it is available (in the CLASSPATH).
   <h5>Log4J</h5>
   As
   <a href="http://jakarta.apache.org/log4j/docs/index.html">Log4J</a>
  -is the prefered/default logger for AXIS,
  +is the prefered/default logger for Axis,
   a <i>few</i> details are presented herein to get the developer going.
   <p>
   Configure Log4J using system properties and/or a properties file:
  @@ -314,7 +314,7 @@
   <code>org.apache.axis.encoding.ser</code>.
   Likewise, setting
   <code>log4j.logger.org.apache.axis=DEBUG</code>
  -will enable debug message for all AXIS classes,
  +will enable debug message for all Axis classes,
   but not for other Jakarta projects.
   <p>
   A combination of settings will enable you to see the log events that
  @@ -346,7 +346,7 @@
   
   <h2>
   <a NAME="Configuration Properties"></a>Configuration Properties</h2>
  -AXIS is in the process of moving away from using system properties
  +Axis is in the process of moving away from using system properties
   as the primary point of internal configuration.
   Avoid calling <code>System.getProperty()</code>,
   and instead call <code>AxisProperties.getProperty</code>.
  @@ -356,14 +356,14 @@
   <p>
   Using this central point of access will allow the
   global configuration system to be redesigned
  -to better support multiple AXIS engines in a
  +to better support multiple Axis engines in a
   single JVM.
   
   <h2>
   <a NAME="Exception Handling"></a>Exception Handling</h2>
  -Guidelines for AXIS Exception Handling are based on best-practices
  +Guidelines for Axis Exception Handling are based on best-practices
   for Exception Handling.
  -While there are details specific to AXIS in these guidelines,
  +While there are details specific to Axis in these guidelines,
   they apply in principle to any project;
   they are included here for two reasons.
   First, because they are not listed elsewhere in the
  @@ -405,19 +405,19 @@
   For command-line tools, this means the <code>main</code>
   method or program.
   For a middleware component, this is the entry point(s) into the component.
  -For AXIS this is <code>AxisServlet</code> or equivalent.
  +For Axis this is <code>AxisServlet</code> or equivalent.
   <p>
   After catching specific exceptions which can be resolved internally,
   the outermost code must ensure that all internally generated exceptions
   are caught and handled.
   While there is generally not much that can be done,
   at a minimum the code should <u>log the exception</u>.
  -In addition to logging, the AXIS Server wraps all such exceptions
  +In addition to logging, the Axis Server wraps all such exceptions
   in AxisFaults and returns them
   to the client code.
   <p>
   This may seem contrary to the primary rule,
  -but in fact we are claiming that AXIS does know
  +but in fact we are claiming that Axis does know
   what to do with this type of exception:
   exit gracefully.
   </ul>
  @@ -474,20 +474,20 @@
   <p>
   <ul>
   <li><h4>Isolate System Logic from Business Logic</h4></li>
  -Exceptions generated by the AXIS runtime
  +Exceptions generated by the Axis runtime
   should be handled, where possible,
  -within the AXIS runtime.
  +within the Axis runtime.
   In the worst case the details of an exception are to be logged
  -by the AXIS runtime,
  +by the Axis runtime,
   and a generally descriptive Exception raised to the Business Logic.
   <p>
   Exceptions raised in the business logic
  -(this includes the server and AXIS handlers)
  +(this includes the server and Axis handlers)
   must be delivered to the client code.
   <p>
   <li><h4>Protect System Code from User Code</h4></li>
  -Protect the AXIS runtime from uncontrolled user business logic.
  -For AXIS, this means that dynamically configurable
  +Protect the Axis runtime from uncontrolled user business logic.
  +For Axis, this means that dynamically configurable
   <code>handlers</code>, <code>providers</code> and other
   user controllable hook-points must be guarded
   by <code>catch(Exception ...)</code>.
  @@ -503,7 +503,7 @@
   This prevents clues as to the nature of the server
   (such as handlers, providers, etc)
   from being revealed to client code.
  -The AXIS component boundries that should be respected are:
  +The Axis component boundries that should be respected are:
   <ul>
   <li>Client Code <--> AxisClient</li>
   <li>AxisClient <--> AxisServlet (AxisServer/AxisEngine)</li>
  @@ -645,12 +645,12 @@
   <h3>
   <a NAME="Interface"></a>Interface</h3>
   
  -AXIS uses the standard Java internationalization class
  +Axis uses the standard Java internationalization class
   <code>java.util.ResourceBundle</code>
   to access property files and message strings,
   and uses <code>java.text.MessageFormat</code>
   to format the strings using variables.
  -AXIS provides a single class <code>org.apache.axis.i18n.Messages</code>
  +Axis provides a single class <code>org.apache.axis.i18n.Messages</code>
   that manages both ResourceBundle and MessageFormat classes.
   Messages methods are:
   
  @@ -660,7 +660,7 @@
   <p><code>public static String getMessage(String key, String var1, String var2)
throws java.util.MissingResourceException;</code>
   <p><code>public static String getMessage(String key, String[] vars) throws
java.util.MissingResourceException;</code>
   
  -<p>AXIS programmers can work with the resource bundle directly via a call
  +<p>Axis programmers can work with the resource bundle directly via a call
   to <code>Messages.getResourceBundle()</code>,
   but the <code>getMessage()</code>
   methods should be used instead for two reasons:
  @@ -710,10 +710,10 @@
   <h3>
   <a NAME="Extending Message Files"></a>Extending Message Files</h3>
   Generally,
  -within AXIS all messages are placed in
  +within Axis all messages are placed in
   org.apache.axis.i18n.resource.properties.
   There are facilities for extending the messages without
  -modifying this file for integration or 3rd party extensions to AXIS.
  +modifying this file for integration or 3rd party extensions to Axis.
   See the <a href="integration-guide.html#Extending Message Files"/>Integration Guide</a>
for details.
   
   <h2>
  @@ -1011,7 +1011,7 @@
   The SOAP messages for all of the tests should appear in the tcpmon window.
   <p>
   <code>tcpmon</code> is described in more detail in the
  -<a href="user-guide.html#tcpmon">AXIS User's Guide</a>.
  +<a href="user-guide.html#tcpmon">Axis User's Guide</a>.
   
   <h4>Using <code>SOAP Monitor</code> to Monitor Functional Tests.</h4>
   <p>
  @@ -1025,7 +1025,7 @@
   monitor window.
   <p>
   <code>SOAP Monitor</code> is described in more detail in the
  -<a href="user-guide.html#soapmon">AXIS User's Guide</a>.
  +<a href="user-guide.html#soapmon">Axis User's Guide</a>.
   
   <h4>Running a Single Functional Test</h4>
   In one window start the server:
  @@ -1037,7 +1037,7 @@
   <blockquote><tt>java junit.swingui.TestRunner -noloading test.wsdl.multithread.MultithreadTestCase</tt></blockquote>
   
   <h4>Turning on Debug Output</h4>
  -This section is oriented to the AXIS default logger: Log4J.
  +This section is oriented to the Axis default logger: Log4J.
   For additional information on Log4J, see the section
   <a href="#Configuring the Logger">Configuring the Logger</a>.
   <p>
  @@ -1068,12 +1068,12 @@
   <p>
   <li>
   If you are building and executing your programs using <code>ant</code>
  -(this includes building AXIS and running it's tests),
  +(this includes building Axis and running it's tests),
   set the environment variable <code>ANT_OPTS</code> to <code>-Dlog4j.configuration=<i>yourConfigFile</i></code>.
   </li>
   <p>
   <li>
  -If you are building AXIS, you can change <code>src/log4j.properties</code>
  +If you are building Axis, you can change <code>src/log4j.properties</code>
   directly.  Be sure NOT to commit your change(s).
   </li>
   </ul>
  @@ -1088,7 +1088,7 @@
   <p>
   <li>
   Set the <i>priority</i> threshold for an appender to <code>DEBUG</code>
  -(The <code>log4j.properties</code> file in AXIS defines two appenders:
  +(The <code>log4j.properties</code> file in Axis defines two appenders:
   <code>CONSOLE</code> and <code>LOGFILE</code>).
   </li>
   </ul>
  @@ -1108,7 +1108,7 @@
   <p>
   <li>
   Set the <i>priority</i> threshold for an appender to <code>DEBUG</code>
  -(The <code>log4j.properties</code> file in AXIS defines two appenders:
  +(The <code>log4j.properties</code> file in Axis defines two appenders:
   <code>CONSOLE</code> and <code>LOGFILE</code>).
   </li>
   <p>
  @@ -1124,7 +1124,7 @@
   </ul>
   
   <h4>Writing Temporary Output</h4>
  -Remember that AXIS is targetted for use in a number
  +Remember that Axis is targetted for use in a number
   of open-source and other web applications,
   and so it needs to be a good citizen.
   Writing output using <code>System.out.println</code> or
  
  
  
  1.6       +2 -2      xml-axis/java/docs/AxisTestRedesign.html
  
  Index: AxisTestRedesign.html
  ===================================================================
  RCS file: /home/cvs/xml-axis/java/docs/AxisTestRedesign.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- AxisTestRedesign.html	7 Nov 2002 07:43:50 -0000	1.5
  +++ AxisTestRedesign.html	11 Jul 2003 23:56:42 -0000	1.6
  @@ -1,10 +1,10 @@
   <HTML>
   <HEAD>
  -<TITLE>AXIS Test Rearchitecture</TITLE>
  +<TITLE>Axis Test Rearchitecture</TITLE>
   <link href="axis.css" rel=stylesheet type=text/css>
   </HEAD>
   <BODY>
  -<H1><CENTER>AXIS Test Rearchitecture</H1></CENTER>
  +<H1><CENTER>Axis Test Rearchitecture</H1></CENTER>
   <a name="top"></a>
   <a href="#quickstart">Quick Start</a><BR>
   <a href="#common">Common Design Principles</a><BR>
  
  
  

Mime
View raw message