gdaniels 02/05/01 05:18:51 Modified: java/docs reference.html Log: Checkpointing a little more work on reference.html Revision Changes Path 1.4 +21 -7 xml-axis/java/docs/reference.html Index: reference.html =================================================================== RCS file: /home/cvs/xml-axis/java/docs/reference.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- reference.html 26 Apr 2002 17:15:36 -0000 1.3 +++ reference.html 1 May 2002 12:18:51 -0000 1.4 @@ -410,9 +410,11 @@ <dt><b><font face="Courier New, Courier, mono"><service name="</font></b><font face="Courier New, Courier, mono"><i>name</i></font><b><font face="Courier New, Courier, mono">" provider="</font></b><font face="Courier New, Courier, mono"><i>provider</i></font><b><font face="Courier New, Courier, mono">" ></font></b></dt> - <dd>Deploys/undeploys an Axis Service. Common options for this element (i.e. - subelements of the form <code><b><parameter name="</b>name<b>" - value="</b>value<b>"/></b>)</code> include: <br> + <dd>Deploys/undeploys an Axis Service. This is the most complex WSDD tag, so + we're going to spend a little time on it.<br> + <br> + <b>Options</b> may be specified as follows : <code><b><parameter name="</b>name<b>" + value="</b>value<b>"/></b></code>, and common ones include:<br> <br> <b>className</b> : the backend implementation class<br> <b>allowedMethods</b> : the allowed methods (use "*" to allow all @@ -433,11 +435,22 @@ <parameter name="className" value="test.Implementation"/> <parameter name="allowedMethods" value="*"/> <namespace>http://testservice/</namespace> - + <requestFlow> <!-- Run these before processing the request --> + <handler type="java:MyHandlerClass"/> + <handler type="somethingIDefinedPreviously"/> + </requestFlow> </service></pre> + <b>Metadata</b> may be specified about particular operations in your service + by using the <operation> tag inside a service. This enables you to map + the java parameter names of a method to particular XML names, to specify the + parameter modes for your parameters, and to map particular XML names to particular + operations.<br> + <br> + <operation name="method"><br> + </operation> <br> </dd> - <dt><b><br> - <font face="Courier New, Courier, mono"><chain name="</font></b><font face="Courier New, Courier, mono"><i>name</i></font><b><font face="Courier New, Courier, mono">"</font></b><b><font face="Courier New, Courier, mono">><br> + <dt> </dt> + <dt><b><font face="Courier New, Courier, mono"><chain name="</font></b><font face="Courier New, Courier, mono"><i>name</i></font><b><font face="Courier New, Courier, mono">"</font></b><b><font face="Courier New, Courier, mono">><br> <<i>subelement</i>/>...<br> </chain> </font></b></dt> <dd>Defines a chain. Each <i>handler</i> (i.e. deployed handler name) in the @@ -451,7 +464,8 @@ or may refer to previously defined <handlers>, with the "type" of the handler referring to the name of the other handler definition:<br> <pre><handler name="logger" type="java:org.apache.axis.handlers.LogHandler"/><br><chain name="myChain"/><br> <handler type="logger"/><br></chain></pre> - </dd> <dt> </dt> + </dd> + <dt> </dt> <dt><b><font face="Courier New, Courier, mono"><transport name="</font></b><font face="Courier New, Courier, mono"><i>name</i></font><b><font face="Courier New, Courier, mono">"></font></b></dt> <dd>Defines a transport on the server side. Server transports are invoked when an incoming request arrives. A server transport may define <b><requestFlow></b>