You are viewing a plain text version of this content. The canonical link for it is here.
Posted to axis-cvs@ws.apache.org by ch...@apache.org on 2005/12/01 07:26:43 UTC
svn commit: r350187 - in /webservices/axis2/trunk/java:
modules/core/src/org/apache/axis2/context/AbstractContext.java
xdocs/Axis2ArchitectureGuide.html
Author: chinthaka
Date: Wed Nov 30 22:26:29 2005
New Revision: 350187
URL: http://svn.apache.org/viewcvs?rev=350187&view=rev
Log:
- implementing what is mentioned here : http://marc.theaimsgroup.com/?l=axis-dev&m=113341827426019&w=2
- Some more stuff on archi guide
Modified:
webservices/axis2/trunk/java/modules/core/src/org/apache/axis2/context/AbstractContext.java
webservices/axis2/trunk/java/xdocs/Axis2ArchitectureGuide.html
Modified: webservices/axis2/trunk/java/modules/core/src/org/apache/axis2/context/AbstractContext.java
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/modules/core/src/org/apache/axis2/context/AbstractContext.java?rev=350187&r1=350186&r2=350187&view=diff
==============================================================================
--- webservices/axis2/trunk/java/modules/core/src/org/apache/axis2/context/AbstractContext.java (original)
+++ webservices/axis2/trunk/java/modules/core/src/org/apache/axis2/context/AbstractContext.java Wed Nov 30 22:26:29 2005
@@ -17,9 +17,11 @@
package org.apache.axis2.context;
import org.apache.axis2.AxisFault;
+import org.apache.axis2.client.Options;
import org.apache.axis2.engine.AxisConfiguration;
import java.util.HashMap;
+import java.util.Iterator;
import java.util.Map;
/**
@@ -91,26 +93,21 @@
// * @param properties
// * @see org.apache.axis2.client.Options#COPY_PROPERTIES
// */
-// public void setProperties(Map properties) {
-// properties = new HashMap();
-// if (properties == null) {
-// this.properties = null;
-// } else {
-// Boolean copyProperties = ((Boolean) properties.get(Options.COPY_PROPERTIES));
-// if (copyProperties != null && copyProperties.booleanValue()) {
-// Iterator iterator = properties.keySet().iterator();
-// while (iterator.hasNext()) {
-// Object key = iterator.next();
-// this.properties.put(key, properties.get(key));
-// }
-// } else {
-// this.properties = properties;
-// }
-// }
-// }
-
- public void setProperties(Map properties) {
- this.properties = properties;
- }
+ public void setProperties(Map properties) {
+ if (properties == null) {
+ this.properties = null;
+ } else {
+ Boolean copyProperties = ((Boolean) properties.get(Options.COPY_PROPERTIES));
+ if (copyProperties != null && copyProperties.booleanValue()) {
+ Iterator iterator = properties.keySet().iterator();
+ while (iterator.hasNext()) {
+ Object key = iterator.next();
+ this.properties.put(key, properties.get(key));
+ }
+ } else {
+ this.properties = properties;
+ }
+ }
+ }
}
Modified: webservices/axis2/trunk/java/xdocs/Axis2ArchitectureGuide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/Axis2ArchitectureGuide.html?rev=350187&r1=350186&r2=350187&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/Axis2ArchitectureGuide.html (original)
+++ webservices/axis2/trunk/java/xdocs/Axis2ArchitectureGuide.html Wed Nov 30 22:26:29 2005
@@ -127,6 +127,12 @@
width="426" height="189" border="0" align="bottom" usemap="#Graphic2Map">
<map name="Graphic2Map">
<area shape="rect" coords="123,31,222,97" href="#bmInfoMod">
+ <area shape="rect" coords="239,62,319,134" href="#bmXML">
+ <area shape="rect" coords="127,112,218,177" href="#bmSOAPPM">
+ <area shape="rect" coords="12,39,89,95" href="#bmDeployment">
+ <area shape="rect" coords="0,108,94,156" href="#bmWSDL">
+ <area shape="rect" coords="350,31,426,86" href="#bmClientAPI">
+ <area shape="rect" coords="350,114,421,164" href="#bmTransports">
</map>
</p>
@@ -173,7 +179,7 @@
of A. A------>B means the given relationship holds between A and B.)</p>
<p>The two hierarchies are connected as shown in the above figure. The
-Description hierarchy represents data that exists throughout the lifetime of
+Description hierarchy represents the static data, may be loaded from a configuration file that exists throughout the lifetime of
Axis2. Examples for such data would be deployed Web Services, operations,
etc. On the other hand, the context hierarchy holds more dynamic information
about things that has more than one instances (e.g.Message Context).</p>
@@ -228,7 +234,7 @@
</td>
<td width="371"><p>This context is avaliable throughout a usage of the
respective service. This can be used to share information between
- several MAPs that belong to the same service, within a single
+ several MEPs that belong to the same service, within a single
interaction.</p>
</td>
<td width="103"><p>Service Description</p>
@@ -263,18 +269,14 @@
</tbody>
</table>
-<p><br>
-<br>
-</p>
-
+<p> </p>
<p>All context classes implement readObject, writeObject methods that allows
-to serialize and de-serialize them correctly. Serializing the current
-Configuration Context object would essentially serialize the whole context
-hierarchy. To restore it, the user has to fist perform the de-serialization
-of the ConfigurationContext object. He can restore the description hierarchy
-by calling the init (axisConfiguration) method of the de-serialized
-ConfigurationContext object.</p>
-
+ to serialize and de-serialize them correctly. Serializing the current
+ Configuration Context object would essentially serialize the whole context
+ hierarchy. To restore it, the user has to fist perform the de-serialization
+ of the ConfigurationContext object. He can restore the description hierarchy
+ by calling the init (axisConfiguration) method of the de-serialized
+ ConfigurationContext object.</p>
<h2><a name="bmXML"></a>XML Processing Model</h2>
<p>Please refer to the <a href="OMTutorial.html">OM Tutorial</a></p>
@@ -289,7 +291,7 @@
Pipes (also named 'Flows'), to perform these two basic actions. Axis Engine
or the driver of Axis2 defines two methods send() and receive() to implement
these two Pipes. The two pipes are named <i>In Pipe</i> and <i>Out Pipe</i>,
-the complex Message Exchange Patterns are constructed by combining these two
+and the complex Message Exchange Patterns are constructed by combining these two
pipes.</p>
<p>Extensibility of the SOAP processing model is provided through the
@@ -300,14 +302,14 @@
<p>The Handlers act as interceptors and they process the parts of the SOAP
message and provide add on services. Usually Handlers work on the SOAP
-Headers yet they may access or change the SOAP Body as well.</p>
+headers yet they may access or change the SOAP Body as well.</p>
-<p>When a SOAP message is send from the Client API, a <i>Out Pipe</i> would
+<p>When a SOAP message is being sent through the Client API, an <i>Out Pipe</i> would
begin, the <i>Out Pipe</i> invokes the Handlers and ends with a Transport
Sender that sends the SOAP message to the target endpoint. The SOAP message
is received by a Transport Receiver at the target endpoint, which reads the
-SOAP message and starts the <i>In Pipe</i>. The In Pipe consists of Handlers
-and ends with a <a href="#mr">Message Receiver</a>, which consumes the SOAP
+SOAP message and starts the <i>In Pipe</i>. The In Pipe consists of handlers
+that ends with a <a href="#mr">Message Receiver</a>, which consumes the SOAP
message.</p>
<p>Above explained processing happens for each and every SOAP message