snichol 2002/06/24 22:29:20 Modified: java/docs/guide rpc.html Log: Add a paragraph about the new service configuration capability to the docs. Revision Changes Path 1.4 +9 -2 xml-soap/java/docs/guide/rpc.html Index: rpc.html =================================================================== RCS file: /home/cvs/xml-soap/java/docs/guide/rpc.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- rpc.html 25 Jun 2002 05:16:27 -0000 1.3 +++ rpc.html 25 Jun 2002 05:29:19 -0000 1.4 @@ -55,7 +55,7 @@ ...)) See the SOAP v1.1 specification for more information on SOAP Faults.</P> <P> -Java services can also be Apache SOAP-aware. Methods which an initial parameter +Java services can also be Apache SOAP-aware. Methods with an initial parameter of type SOAPContext can be invoked by a SOAP RPC call that passes the other parameters. The provider will invoke the method with the SOAPContext of the current request as the first parameter. The SOAPContext includes a bag (Hashtable) of instances, @@ -65,7 +65,14 @@ This mechanism provides services with the ability to access a great deal of information about the environment in which they are executing. </P> -<P>Last updated 6/17/2002 by Scott Nichol <<A href="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED]</A>>.</P> +<P> +Java services can also use an Apache SOAP-provided interface ConfigurableService to receive +initialization parameters. Upon instantiation, a service implementing this interface +will have the configure method called. The parameters for this method are hashtables +of initialization parameters for the service (from the deployment descriptor options tags), +the servlet and the servlet context (web application). +</P> +<P>Last updated 6/24/2002 by Scott Nichol <<A href="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED]</A>>.</P> </body>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
