scheu 02/04/25 11:51:06
Modified: java/docs developers-guide.html
Log:
A couple additions and corrections to the developer's doc
Revision Changes Path
1.14 +11 -22 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.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- developers-guide.html 19 Mar 2002 15:42:01 -0000 1.13
+++ developers-guide.html 25 Apr 2002 18:51:06 -0000 1.14
@@ -57,12 +57,21 @@
Conventions for the Java Programming Language"</a></li>
<li>
+When fixing a <a
href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Axis&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.bug_id";>
+"Axis Bugzilla Bug"</a> include the href of the
+bug in the cvs commit message.</li>
+
+<li>
Incompatible changes to
<a href="user-guide.html#published interfaces">published Axis interfaces</a>
should be avoided where possible.
When changes are necessary, for example to maintain or improve the overall
modularity of Axis, the
impact on users must be considered and, preferably, documented.</li>
+
+<li>
+If you are making a big change that may affect interoperability, please
+run the <a href="http://xml.apache.org/~rubys/echotest.pl";>echotest2 round 2
interop test</a> to ensure that your change does not result in any new interop
failures. You will also need the <a
href="http://xml.apache.org/~rubys/client_deploy.wsdd";>client_deploy.wsdd</a>. Here
are the <a href="http://xml.apache.org/~rubys/ApacheClientInterop.html";>nightly
interop test results</a>.
</ul>
<h2>
@@ -458,10 +467,6 @@
<font color="#000000">Ran the Wsdl2java emitter to create java files:</font></li>
<br>
-<p>
-<br>
-<br>
-<br>
<p><tt><font color="#993366">java org.apache.axis.wsdl.Wsdl2java -t -s
SequenceTest.wsdl</font></tt>
<br>
@@ -474,11 +479,6 @@
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>
-
-<br>
-<p>
-<br>
-<br>
<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.
@@ -486,9 +486,6 @@
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
need to make sure that your <wsdl2java ...> clause generates a
skeleton).</font></li>
-</ol>
-
-<ol>
<li>
<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,
@@ -502,11 +499,7 @@
controls the building of the tests. Locate the "wsdl-setup" target.
You will see a clause that runs the Wsdl2java code:</font></li>
-<br>
-<p>
-<br>
-<br>
-<br>
+
<br>
<p><tt><font color="#993366"><ant
antfile="test/wsdl/Wsdl2javaTestSuite.xml"/></font></tt>
<p><font color="#000000">Following this clause you will see some clauses
@@ -520,11 +513,7 @@
This file contains the clauses to run wsdl2java. Add a wsdl2java
clause. Here is the one for SequenceTest:</font></li>
-<br>
-<p>
-<br>
-<br>
-<br>
+
<br>
<p><tt><font color="#663366"> </font><font color="#993366"><!--
Sequence Test --></font></tt>
