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 rk...@apache.org on 2003/08/09 16:12:12 UTC
cvs commit: xml-axis/java/docs developers-guide.html
rkellogg 2003/08/09 07:12:12
Modified: java/docs developers-guide.html
Log:
Correct consistency errors with spelling of Axis and Java. Fixed grammatical errors.
Revision Changes Path
1.39 +15 -15 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.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- developers-guide.html 9 Aug 2003 12:54:39 -0000 1.38
+++ developers-guide.html 9 Aug 2003 14:12:12 -0000 1.39
@@ -79,7 +79,7 @@
The following packages are required for axis development:
<ul>
<li>
-<a href="http://jakarta.apache.org/ant/index.html">ant </a>- java based build tool. <B>Please Note: Version 1.5 OR HIGHER is required</B></li>
+<a href="http://jakarta.apache.org/ant/index.html">ant </a>- Java based build tool. <B>Please Note: Version 1.5 OR HIGHER is required</B></li>
<li>
<a href="http://www.junit.org">junit</a> - testing package</li>
@@ -91,7 +91,7 @@
Install Java 1.3.1 JDK (or later).</li>
</ul>
-<p><br>The axis jar files are built in the <tt>xml-axis/java/build/lib</tt>
+<p><br>The Axis jar files are built in the <tt>xml-axis/java/build/lib</tt>
directory. Here is an example CLASSPATH, which I use when developing
code:
<blockquote>
@@ -118,7 +118,7 @@
<h3>
<a NAME="Discovery"></a>Discovery</h3>
-An axis-specific component factory should be created of the form:
+An Axis-specific component factory should be created of the form:
<ol>
org.apache.axis.components.<componentType>.<factoryClassName>
</ol>
@@ -351,7 +351,7 @@
supports a number of standard query strings (<i>?list</i>, <i>?method</i>, and <i>?wsdl</i>) that
provide information from or perform operations on a web service (for instance, <i>?method</i> is
used to invoke a method on a web service and <i>?wsdl</i> is used to retrieve the WSDL document for
-a web service). Axis serlvets are not limited to these three query strings and developers may
+a web service). Axis servlets are not limited to these three query strings and developers may
create their own "plug-ins" by implementing the <code>org.apache.axis.transport.http.QSHandler</code>
interface. There is one method in this interface that must be implemented, with the following signature:
<pre>
@@ -450,8 +450,8 @@
<h2>
<a NAME="Exception Handling"></a>Exception Handling</h2>
-Guidelines for Axis Exception Handling are based on best-practices
-for Exception Handling.
+Guidelines for Axis exception handling are based on best-practices
+for exception handling.
While there are details specific to Axis in these guidelines,
they apply in principle to any project;
they are included here for two reasons.
@@ -588,7 +588,7 @@
<p>
<li><h4>Isolate Visibility into Server from Client</h4></li>
Specific exceptions should be logged at the server side,
-and more a general exception thrown to the client.
+and a more general exception thrown to the client.
This prevents clues as to the nature of the server
(such as handlers, providers, etc)
from being revealed to client code.
@@ -871,7 +871,7 @@
the webservice.</font></li>
<BR>
<li>
-<font color="#000000">Ran the Wsdl2java emitter to create java files:</font></li>
+<font color="#000000">Ran the Wsdl2java emitter to create Java files:</font></li>
<p><tt><font color="#993366">java org.apache.axis.wsdl.Wsdl2java -t -s
SequenceTest.wsdl</font></tt>
<br>
@@ -880,19 +880,19 @@
<font color="#000000">The -t option causes the emitter to generate a *TestCase.java
file that hooks into the test harness. This file is operational without
any additional changes. Copy the *TestCase.java file into the same
-directory as your wsdl file. (Ideally only the java files that are
+directory as your wsdl file. (Ideally only the Java files that are
changed need to be in your directory. So this file is not needed,
but please make sure to modify your <wsdl2java ...> clause (described
below) to emit a testcase.</font></li>
<li>
<font color="#000000">The -s option causes the emitter to generate a *SOAPBindingImpl.java
-file. The java file contains empty methods for the service.
+file. The Java file contains empty methods for the service.
You probably want to fill them in with your own logic. Copy the *SOAPBindingImpl.java
file into the same directory as your wsdl file. (If no changes are
-needed in the java file, you don't need to save it. But you will
+needed in the Java file, you don't need to save it. But you will
need to make sure that your <wsdl2java ...> clause generates a skeleton).</font></li>
<li>
-<font color="#000000">Remove all of the java files that don't require modification.
+<font color="#000000">Remove all of the Java files that don't require modification.
So you should have three files in your directory (wsdl file, *TestCase.java,
and *SOAPBindingImpl.java). My sequence test has an another file
due to some additional logic that I needed.</font></li>
@@ -997,7 +997,7 @@
...
</pre>
<p>
-Actually, Jdk14Logger does implement Log. What you have is a JUnit classloading
+Actually, the Jdk14Logger does implement Log. What you have is a JUnit classloading
issue. JUnit's graphical TestRunner has a feature where it will dynamically
reload modified classes every time the user presses the "Run" button. This way,
the user doesn't need to relaunch the TestRunner after every edit. For this,
@@ -1143,7 +1143,7 @@
<ul>
<p>
<li>
-If you are building and executing <code>java</code> programs from
+If you are building and executing <code>Java</code> programs from
a command line or script file,
include the JVM option
<code>-Dlog4j.configuration=<i>yourConfigFile</i></code>.
@@ -1213,7 +1213,7 @@
</ul>
<h4>Writing Temporary Output</h4>
-Remember that Axis is targetted for use in a number
+Remember that Axis is targeted 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