ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Ws Wiki] Update of "FrontPage/Axis2/MessageContextSaveRestore" by AnnRobinson
Date Tue, 31 Oct 2006 20:43:29 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.

The following page has been changed by AnnRobinson:

+ Because of the complexity of the AXIS2 message context, there are two
+ important design points:                                             
+ 1. Save runtime data but not deployment or configuration data.
+    This cuts down on the amount of data that needs to be saved and      
+    restored.  This also means that only a subset of the message context 
+    object graph graph needs to be saved.  Then, when the message context
+    is restored, the object graph is re-populated with a mix of restored 
+    objects and objects from the current AXIS2 engine.                   
+ 2. Have an object save/restore its own state.
+    This is standard object-oriented design.  An object controls its own  
+    state and is best to determine what parts of its data need to be saved
+    and restored.  This should also help to reduce problems as developers 
+    make changes to the object over time:  it's easier to update the      
+    object's save/restore functions rather than putting requirements on   
+    external component code. In conjunction with this design point, the   
+    object should use the interface in order to    
+    customize the serialization of an object's state                      
+ This approach results in having the following objects as major
+ participants in the message context serialization:            
+  MessageContext     
+  OperationContext   
+  ServiceContext     
+  ServiceGroupContext
+  SessionContext     
+  Options            

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message