You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by rs...@apache.org on 2002/10/01 23:32:32 UTC
cvs commit: xml-axis/java/docs integration-guide.html
rsitze 2002/10/01 14:32:32
Modified: java/docs integration-guide.html
Log:
1. Commented some sections out, until we have a better story.
2. Left a few as place holders for future, with comments that we don't have a story yet..
3. Other minor cleanup.
The only section I have any real concerns about is the WSDL topic.
It's out of my league. It may be that some portion of it is not
really appropriate for integration... but more appropriate for a
users guide.
Revision Changes Path
1.13 +25 -44 xml-axis/java/docs/integration-guide.html
Index: integration-guide.html
===================================================================
RCS file: /home/cvs/xml-axis/java/docs/integration-guide.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- integration-guide.html 29 Sep 2002 04:28:14 -0000 1.12
+++ integration-guide.html 1 Oct 2002 21:32:31 -0000 1.13
@@ -29,7 +29,8 @@
Table of Contents</h3>
<a href="#Introduction">Introduction</a>
<br><a href="#Pluggable APIs">Pluggable APIs</a>
-<br> <a href="#System Management Plug">System Management</a>
+<!-- <br> <a href="#System Management Plug">System Management</a>
+-->
<br> <a href="#Logging/Tracing Plug">Logging/Tracing</a>
<br> <a href="#Configuration Plug">Configuration</a>
<br> <a href="#Handlers Plug">Handlers</a>
@@ -52,6 +53,7 @@
<a NAME="Pluggable APIs"></a>Pluggable APIs</h2>
The following are the points that are pluggable in order to integrate AXIS
into a web application server.
+<!--
<h3>
<a NAME="System Management Plug"></a>System Management</h3>
What points are necessary to manage AXIS?
@@ -87,6 +89,7 @@
<li>
Example</li>
</ul>
+-->
<h3><a NAME="Logging/Tracing Plug"></a>Logging/Tracing</h3>
AXIS logging and tracing is based on the Logging component of the
@@ -251,7 +254,7 @@
<code>AxisClient = new AxisClient(config);</code>
</ul>
<br>The details may vary (server versus client, whether other factories are involved, etc).
-Regardless, the point is that user code is responsible for
+Regardless, the point is that integration code is responsible for
calling <code>EngineConfigurationFactoryFinder(someContext)</code>
and ensuring that the results are handed to AXIS.
<code>someContext</code> is key to how the factory finder
@@ -274,8 +277,8 @@
</li>
<li>Locate all resources named
<code>META-INF/services/org.apache.axis.EngineConfigurationFactory</code>.
-Each line of such a file identifies the name of a class
-implementing the interface.
+Each line of such a resource identifies the name of a class
+implementing the interface ('#' comments, through end-of-line).
</li>
<li>
<code>org.apache.axis.configuration.EngineConfigurationFactoryServlet</code>
@@ -301,7 +304,7 @@
<li>
The implementation class is required to examine runtime environment
(to optionally include the parameter).
-If the environment can provide informatin required by
+If the environment can provide information required by
an EngineConfigurationFactory,
then the <code>newFactory()</code> may return in instance of that factory.
Otherwise, <code>newFactory()</code> must return null.
@@ -332,13 +335,15 @@
from the current working directory!).
<p>The default Servlet factory will open the Web Application resource
-<code>/WEB-INF/server-config.wsdd</code>:
+<code>/WEB-INF/server-config.wsdd</code>
+(The name of this file may be changed using the
+system property <code>axis.ServerConfigFile</code>):
<ul>
<li>
-If it exists as a accessible file (i.e. not in a JAR/WAR file),
-then it opens it as a file
-(this allows changes to be saved,
-if changes are allowed & made using the Admin tools).
+If it exists as an accessible file (i.e. not in a JAR/WAR file),
+then it opens it as a file.
+This allows changes to be saved,
+if changes are allowed & made using the Admin tools.
</li>
<li>
If it does not exist as a file, then an attempt is made
@@ -380,39 +385,8 @@
<h3>
<a NAME="Handlers Plug"></a>Handlers</h3>
-What new handlers might a system integrator wish to implement?
-<ul>
-<li>
-Justification/Rationale - why is this plug point necessary? Spec
-compliance?</li>
-
-<li>
-Interfaces</li>
-
-<li>
-Mechanism</li>
-
-<ul>
-<li>
-Life cycle</li>
-
-<li>
-Exception handling - in general; plug-in shouldn't throw any exceptions
-- does runtime ignore? Log?)</li>
-
-<li>
-Multiple thread support? Ie., is synchronization required?</li>
-</ul>
-
-<li>
-Configuration/reconfiguration</li>
-
-<li>
-Default behavior if not plugged.</li>
-
-<li>
-Example</li>
-</ul>
+See the <a href="architecture-guide.html">Architecture
+Guide</a> for current information on Handlers.
<h3>
<a NAME="Internationalization Plug"></a>Internationalization</h3>
@@ -592,7 +566,8 @@
<h3>
<a NAME="Performance Monitoring Plug"></a>Performance Monitoring</h3>
-How can we monitor the performance of AXIS?
+AXIS does not yet include specific Performance Monitoring Plugs.
+<!--
<ul>
<li>
Justification/Rationale - why is this plug point necessary? Spec
@@ -625,9 +600,12 @@
<li>
Example</li>
</ul>
+-->
<h3>
<a NAME="Encoding Plug"></a>Encoding</h3>
+AXIS does not yet include an Encoding Plug.
+<!--
How can a system integrator plug in other encoding mechanisms such as SOAP
1.2 or optimized XML-based encoding?
<ul>
@@ -662,7 +640,9 @@
<li>
Example</li>
</ul>
+-->
+<!--
<h3>
<a NAME="Compiler"></a>Compiler</h3>
How can a system integrator plug in other encoding mechanisms such as SOAP
@@ -699,6 +679,7 @@
<li>
Example</li>
</ul>
+-->
<h3>
<a NAME="WSDL plug"></a>WSDL Parser and Code Generator Framework</h3>