nagy 01/06/29 08:03:58
Modified: java/docs/guide config.html interop.html manage.html
Log:
Updated User's Guide to reflect recent changes in codebase
Revision Changes Path
1.5 +31 -5 xml-soap/java/docs/guide/config.html
Index: config.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/guide/config.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- config.html 2001/05/21 20:19:06 1.4
+++ config.html 2001/06/29 15:03:57 1.5
@@ -49,25 +49,51 @@
<P>where <B><I>config-file</I></B> is the path (either fully qualified or relative)
and filename of the SOAP configuration file.<BR>
</P>
-<p><A name="configfile"></A>There is only one setting currently allowed
+<p><A name="configfile"></A>There are two settings currently allowed
in the SOAP server configuration file: information
+about the Service Manager and information
about the <a href="#pcm">pluggable configuration manager</a>. A SOAP server
configuration file which
-sets information about the provider would
-look like the following:<pre> <!-- Sample Apache SOAP Server Configuration
File -->
+sets information about both the Service Manager
+and the configuration manager would look
+like the following:<pre> <!-- Sample Apache SOAP Server Configuration File
-->
<soapServer>
<!-- This section defines the same thing you get if you don't -->
<!-- specify anything at all - aka the default -->
+ <serviceManager>
+ <option name="SOAPInterfaceEnabled"
value="<B><I>boolean-value</I></B>" />
+ </serviceManager>
<configManager value="<B><I>config-manager</I></B>" >
[<option name="<B><I>option-name</I></B>"
value="<B><I>option-value</I></B>"/>]*
</configManager>
</soapServer></pre>
-<P>where <B><I>config-manager</I></B> is the fully qualified class name of the
+<P>where <B><I>boolean-value</I></B> is either true or false, depending upon
+whether or not you want the SOAP interface
+to the Service Manager to be enabled, and
+<B><I>config-manager</I></B> is the fully qualified class name of the
configuration manager which should be used
by the SOAP server. Additional information
may be passed to the configuration manager
through the use of <option> elements,
with <B><I>option-name</I></B> and<B><I> option-value</I></B> acting as key/value
pairs.</P>
<HR>
+<H3><A name="smaccess">Controlling Access to the ServiceManager</A></H3>
+<P>Although the SOAP interface for deploying/undeploying
+services can be very useful during development,
+it is not always desirable to expose such
+capabilities in a runtime environment. Apache
+SOAP provides the ability to enable/disable
+the SOAP interface to the ServiceManager
+by setting a boolean flag in the <A href="#configfile">configuration file</A>. If
the flag is set to true, or if it is
+not present, then the SOAP interface is enabled.
+If it is set to false, then the ServiceManagerClient,
+as well as any other client which uses that
+interface, will not be able to communicate
+with the ServiceManager. However, anything
+which communicates with the ServiceManager
+directly, such as the admin JSP pages, will
+still be able to alter the state of the ServiceManager.
+</P>
+<HR>
<h3><A name="pcm"/>Pluggable Configuration Manager</A></h3>
<P>The SOAP configuration manager is responsible
for saving the current list of deployed services
@@ -169,7 +195,7 @@
</blockquote><p>As is noted in the section <A href="#configfile">above</A>,
your configuration manager can be passed
parameters via <option> elements in
the SOAP server configuration file.
-<P>Last updated 5/20/2001 by Bill Nagy <<A
href="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED]</A>>.</P>
+<P>Last updated 6/28/2001 by Bill Nagy <<A
href="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED]</A>>.</P>
</body>
1.3 +15 -13 xml-soap/java/docs/guide/interop.html
Index: interop.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/guide/interop.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- interop.html 2001/05/25 19:12:44 1.2
+++ interop.html 2001/06/29 15:03:57 1.3
@@ -1,9 +1,10 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
-<meta name="GENERATOR" content="Microsoft FrontPage Express 2.0">
+<META name="GENERATOR" content="IBM WebSphere Homepage Builder V4.0.0 for Linux">
<title>Interoperability with Other SOAP Implementations</title>
</head>
@@ -91,18 +92,18 @@
May 2001. Apache SOAP currently behaves as follows:</p>
<ul>
- <li><p align="left">Built-in serializers for the Java types
- corresponding to various XML Schema simple types will by
- default indicate the resulting type using XML Schema from
- the 1999 namespace. If it is desired to use one of the
- other schema namespaces in the SOAP envelopes generated
- by Apache SOAP, then one has to edit org/apache/soap/Constants.java
- and change the values of the constants
- NS_URI_CURRENT_SCHEMA_XSI and NS_URI_CURRENT_SCHEMA_XSD
- to the selected ones (indicated right before these
- constants). Once built, the resulting system will
- generate SOAP envelopes using the desired target
- namespace.<br>
+ <li><p align="left">Built-in serializers for the Java types corresponding
+ to various XML Schema simple types will by
+ default indicate the resulting type using
+ XML Schema from the 2001 namespace. If it
+ is desired to use one of the other schema
+ namespaces in the SOAP envelopes generated
+ by Apache SOAP, then one has to edit org/apache/soap/Constants.java
+ and change the values of the constants NS_URI_CURRENT_SCHEMA_XSI
+ and NS_URI_CURRENT_SCHEMA_XSD to the selected
+ ones (indicated right before these constants).
+ Once built, the resulting system will generate
+ SOAP envelopes using the desired target namespace.<br>
</p>
</li>
<li><p align="left">Apache SOAP will correctly deserialize
@@ -288,5 +289,6 @@
the SOAP Builders forum. It provides a fairly comprehensive
example of implementing a non-trivial interoperable Web service
and service client.</p>
+<P>Last updated 6/28/2001 by Bill Nagy <<A
href="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED]</A>>.</P>
</body>
</html>
1.4 +8 -1 xml-soap/java/docs/guide/manage.html
Index: manage.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/guide/manage.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- manage.html 2001/05/21 22:31:40 1.3
+++ manage.html 2001/06/29 15:03:57 1.4
@@ -156,6 +156,13 @@
<p>where foo.xml is the deployment descriptor and the URL is
appropriate for your installation.</p>
-<P>Last updated 5/19/2001 by Bill Nagy <<A
href="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED]</A>>.</P>
+<P><I><B>Note</B></I>: <I>If you set the SOAPInterfaceEnabled option
+to false in the soap.xml file, then users
+will be prevented from being able to manipulate
+services via the ServiceManagerClient. However,
+they will still be able to do so through
+the admin JSP pages. For more information
+on controlling the ServiceManager, look <A
href="config.html#smaccess">here</A>.</I></P>
+<P>Last updated 6/28/2001 by Bill Nagy <<A
href="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED]</A>>.</P>
</body>
</html>
