axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dee...@apache.org
Subject svn commit: r208724 - /webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html
Date Fri, 01 Jul 2005 07:35:21 GMT
Author: deepal
Date: Fri Jul  1 00:35:19 2005
New Revision: 208724

URL: http://svn.apache.org/viewcvs?rev=208724&view=rev
Log:
modified (server.xml ---> axis2.xml)

Modified:
    webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html

Modified: webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html?rev=208724&r1=208723&r2=208724&view=diff
==============================================================================
--- webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html (original)
+++ webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html Fri Jul  1 00:35:19 2005
@@ -249,8 +249,8 @@
 <p>There deployment Model provides a concrete mechanism to configure Axis2. Deployment
Model has four entities that provide the configuration. </p>
 
 
-<h3>The <em>server.xml</em> file and <em>client.xml</em> files
</h3>
-<p>These two files holds the global configuration for the client and server, and provide
following information.</p>
+<h3>The <em>axis2.xml</em> file </h3>
+<p>This file holds the global configuration for the client and server, and provide
following information.</p>
 <ol>
 <li>The global parameters</li>
 <li>Registered transports in and transport outs </li>
@@ -269,7 +269,7 @@
 <h3>Module Archive</h3> 
 <p>Module archive must have a <em>META-INF/module.xml</em> file and dependent
classes the <em>module.xml</em> file has Module parameters and the Operations
defined in  the module.</p>
 
-<p>When the system started up the Axis2 ask the deployment model  to create a Axis
Configuration, the Deployment Model first find a <em>server.xml</em> or a <em>client.xml</em>
file and build the global configuration. Then the Deployment check for the Module archives
and then for the service archives, the corresponding services and Modules are added to the
Axis Configuration. System will build Contexts on top of the Axis Configurations and the Axis2
is ready to send or receive the SOAP Message. The Hot deployment is allowed only for the Service
and in that case a thread will check the repository repeatedly, and add the Service corresponds
to the new found Service archives to the repository.
+<p>When the system started up the Axis2 ask the deployment model  to create a Axis
Configuration, the Deployment Model first find a <em>axis2.xml</em> file and build
the global configuration. Then the Deployment check for the Module archives and then for the
service archives, the corresponding services and Modules are added to the Axis Configuration.
System will build Contexts on top of the Axis Configurations and the Axis2 is ready to send
or receive the SOAP Message. The Hot deployment is allowed only for the Service and in that
case a thread will check the repository repeatedly, and add the Service corresponds to the
new found Service archives to the repository.
     </p>
 
 



Mime
View raw message