glyn 02/03/18 08:03:44
Modified: java/docs user-guide.html architecture-guide.html
Log:
Migrate beta fix.
Revision Changes Path
1.48 +32 -30 xml-axis/java/docs/user-guide.html
Index: user-guide.html
===================================================================
RCS file: /home/cvs/xml-axis/java/docs/user-guide.html,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- user-guide.html 14 Mar 2002 22:25:14 -0000 1.47
+++ user-guide.html 18 Mar 2002 16:03:44 -0000 1.48
@@ -189,9 +189,9 @@
<div class="example">
<pre>1 import org.apache.axis.client.Call;
2 import org.apache.axis.client.Service;
-3
-4 public class TestClient
-5 {
+3 import javax.xml.rpc.namespace.QName;
+4
+5 public class TestClient {
6 public static void main(String [] args) {
7 try {
8
String endpoint =
@@ -1142,13 +1142,13 @@
<p>Where:
<ul>
<li>
--o indicates the name of the <b><i>output wsdl</i></b> file</li>
+-o indicates the name of the <b><i>output WSDL</i></b> file</li>
<li>
-l indicates the<b><i> location of the service</i></b></li>
<li>
--n is the target <b><i>namespace</i></b> of the wsdl file</li>
+-n is the target <b><i>namespace</i></b> of the WSDL file</li>
<li>
-p indicates a mapping from the <b><i>package to a namespace</i></b>.
@@ -1157,7 +1157,7 @@
<li>
the class specified contains the interface of the webservice.</li>
</ul>
-The output wsld document will contain the appropriate wsdl types, messages,
+The output WSDL document will contain the appropriate WSDL types, messages,
portType, bindings and service descriptions to support a SOAP rpc, encoding
web service. If your specified interface methods reference other
classes, the Java2WSDL tool will generate the appropriate xml types to
@@ -1180,7 +1180,7 @@
<br><tt><font color="#993366">
-o, --output <argument></font></tt>
<br><tt><font
color="#993366">
-output Wsdl filename</font></tt>
+output WSDL filename</font></tt>
<br><tt><font color="#993366">
-l, --location <argument></font></tt>
<br><tt><font
color="#993366">
@@ -1212,15 +1212,15 @@
<br><tt><font color="#993366">
-L, --locationImport <argument></font></tt>
<br><tt><font
color="#993366">
-location of interface wsdl</font></tt>
+location of interface WSDL</font></tt>
<br><tt><font color="#993366">
-N, --namespaceImpl <argument></font></tt>
<br><tt><font
color="#993366">
-target namespace for implementation wsdl</font></tt>
+target namespace for implementation WSDL</font></tt>
<br><tt><font color="#993366">
-O, --outputImpl <argument></font></tt>
<br><tt><font
color="#993366">
-output Implementation Wsdl filename, setting this causes --outputWsdlMode
+output Implementation WSDL filename, setting this causes --outputWsdlMode
to be ignored</font></tt>
<br><tt><font color="#993366">
-f, --factory <argument></font></tt>
@@ -1250,9 +1250,9 @@
<br>
<p><b>-h , --help</b>
<br>Prints the help message.
-<p><b>-o, --output <wsdl file></b>
-<br>Indicates the name of the output wsdl file. If not specified,
-a suitable default wsdl file is written into the current directory.
+<p><b>-o, --output <WSDL file></b>
+<br>Indicates the name of the output WSDL file. If not specified,
+a suitable default WSDL file is written into the current directory.
<p><b>-l, --location <location></b>
<br>Indicates the url of the location of the service. The name after
the last slash or backslash is the name of the service port (unless overriden
@@ -1260,12 +1260,12 @@
assigned the specified value.
<p><b>-s, -service <name></b>
<br>Indicates the name of the service. If not specified, the service
-name is derived from the --location value. The names of the wsdl
+name is derived from the --location value. The names of the WSDL
binding, service, and port elements are derived from the service name as
indicated in the <tt><font color="#993366">Details</font></tt> section
above.
<p><b>-n, --namespace <target namespace></b>
-<br>Indicates the name of the target namespace of the wsdl.
+<br>Indicates the name of the target namespace of the WSDL.
<p><b>-p, --PkgToNS <package> <namespace></b>
<br>Indicates the mapping of a package to a namespace. If a package
is encountered that does not have a namespace, the Java2WSDL emitter will
@@ -1273,36 +1273,36 @@
multiple times.
<p><b>-m, --methods <arguments></b>
<br>If this option is specified, only the indicated methods in your interface
-class will be exported into the wsdl file. The methods list must
+class will be exported into the WSDL file. The methods list must
be comma separated. If not specified, all methods declared in the
-interface class will be exported into the wsdl file.
+interface class will be exported into the WSDL file.
<p><b>-a, --all</b>
<br>If this option is specified, the Java2WSDL parser will look into extended
-classes to determine the list of methods to export into the wsdl file.
+classes to determine the list of methods to export into the WSDL file.
<p><b>-w, --outputWSDLMode <mode></b>
-<br>Indicates the kind of wsdl to generate. Accepted values are:
+<br>Indicates the kind of WSDL to generate. Accepted values are:
<ul>
<li>
All --- (default) Generates wsld containing both interface and implementation
-wsdl constructs.</li>
+WSDL constructs.</li>
<li>
-Interface --- Generates a wsdl containing the interface constructs (no
+Interface --- Generates a WSDL containing the interface constructs (no
service element).</li>
<li>
-Implementation -- Generates a wsdl containing the implementation.
-The interface wsdl is imported via the -L option.</li>
+Implementation -- Generates a WSDL containing the implementation.
+The interface WSDL is imported via the -L option.</li>
</ul>
<b>-L, --locationImport <url></b>
-<br>Used to indicate the location of the interface wsdl when generating
-an implementation wsdl.
+<br>Used to indicate the location of the interface WSDL when generating
+an implementation WSDL.
<p><b>-N, --namespaceImpl <namespace></b>
-<br>Namespace of the implementation wsdl.
-<p><b>-O, --outputImpl <wsdl file></b>
-<br>Use this option to indicate the name of the output implementation wsdl
+<br>Namespace of the implementation WSDL.
+<p><b>-O, --outputImpl <WSDL file></b>
+<br>Use this option to indicate the name of the output implementation WSDL
file. If specified, Java2WSDL will produce interface and implementation
-wsdl files. If this option is used, the -w option is ignored.
+WSDL files. If this option is used, the -w option is ignored.
<p><b>-f, --factory <class></b>
<br>Use this expert option to extend and customize the WSDL2Java tool.
<p><b>-i, --implClass <impl-class></b>
@@ -1316,7 +1316,7 @@
could be the actual implementation class, a stub class or a skeleton class.
<h4>
Step 3: Create Bindings using WSDL2Java</h4>
-Use the generated wsdl file to build the appropriate client/server bindings
+Use the generated WSDL file to build the appropriate client/server bindings
for the web service (see <a href="#WSDL2Java: Building stubs, skeletons, and
data">WSDL2Java</a>):
<div class="example"><br><font face="Courier New,Courier">% java
org.apache.axis.wsdl.Wsdl2java -o . -d session -s -Nurn:Example6
samples.userguide.example6 ws.wsdl</font></div>
<p>This will generate the following files:
@@ -1485,6 +1485,8 @@
and record a new response. This is particularly handy in that you can edit
the XML in the request window before resending - so you can use this as
a great tool for testing the effects of different XML on SOAP servers.
+Note that you may need to change the content-length HTTP header value
+before resending an edited request.
<dl>
<dt>
</dt>
1.9 +2 -2 xml-axis/java/docs/architecture-guide.html
Index: architecture-guide.html
===================================================================
RCS file: /home/cvs/xml-axis/java/docs/architecture-guide.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- architecture-guide.html 15 Mar 2002 10:19:35 -0000 1.8
+++ architecture-guide.html 18 Mar 2002 16:03:44 -0000 1.9
@@ -268,7 +268,7 @@
<h3>
WSDD-Based Administration</h3>
WSDD is an XML grammer for deployment descriptors which are used to
-statically configuring Axis engines.
+statically configure Axis engines.
Each Handler needs configuration in terms of the concrete class name
of a factory for the Handler, a set of options for the handler, and
a lifecycle scope value which determines the scope of sharing of
@@ -428,7 +428,7 @@
SOAP-specific and HTTP-specific features?</li>
<li>
-The Axis Engine currently knows about thee layers of handlers: transport,
+The Axis Engine currently knows about three layers of handlers: transport,
global, and service. However, architecturally, this is rather odd. What
"law" of web services ensures that there will always and only ever be <i>three</i>
layers? It would be more natural to use Targeted Chains with their more
