Author: damitha
Date: Wed Jan 10 21:49:06 2007
New Revision: 495133

URL: http://svn.apache.org/viewvc?view=rev&rev=495133
Log:
Updated documentation

Modified:
    webservices/sandesha/trunk/c/INSTALL
    webservices/sandesha/trunk/c/README

Modified: webservices/sandesha/trunk/c/INSTALL
URL: 
http://svn.apache.org/viewvc/webservices/sandesha/trunk/c/INSTALL?view=diff&rev=495133&r1=495132&r2=495133
==============================================================================
--- webservices/sandesha/trunk/c/INSTALL (original)
+++ webservices/sandesha/trunk/c/INSTALL Wed Jan 10 21:49:06 2007
@@ -2,11 +2,11 @@
 =================
 
 1. Getting Sandesha2C working with the source release on Linux
-    - This version of Sandesha2C depends on Axis2C 0.92
+    - This version of Sandesha2C depends on Axis2C 0.95
         - Download Axis2C from http://ws.apache.org/axis2/c/download.cgi and
           install.
     - Go to Sandesha2C source directory
     - Run configure with AXIS2 include path.
         ./configure --prefix=<install_dir> --enable-static=no 
--with-axis2=<axis2_install_path>
     - Run make and make install
-    
+   

Modified: webservices/sandesha/trunk/c/README
URL: 
http://svn.apache.org/viewvc/webservices/sandesha/trunk/c/README?view=diff&rev=495133&r1=495132&r2=495133
==============================================================================
--- webservices/sandesha/trunk/c/README (original)
+++ webservices/sandesha/trunk/c/README Wed Jan 10 21:49:06 2007
@@ -12,7 +12,7 @@
   
   The Latest Version
   ------------------
-  Sandesha2C is its ealy ages and not release yet.
+  Sandesha2C is its early ages and not release yet.
 
   Documentation
   -------------
@@ -33,3 +33,93 @@
   ---------
   Please see the file called LICENSE.
 
+  How To Run.
+  ----------
+  Install sandesha2 module into axis2/modules folder. Add the RMPhase
+  information into axis2.xml as following. Search for 'RMPhase' in the
+  following xml block to identify the RM specific entries.
+
+    <!-- ================================================= -->
+    <!-- Phases  -->
+    <!-- ================================================= -->
+    <phaseOrder type="inflow">
+        <!--  System pre defined phases       -->
+        <phase name="TransportIn"/>
+        <phase name="PreDispatch"/>
+        <phase name="Dispatch">
+            <handler name="AddressingBasedDispatcher"
+                     class="axis2_engine">
+                <order phase="Dispatch"/>
+            </handler>
+             <handler name="RequestURIBasedDispatcher"
+                     class="axis2_engine">
+                <order phase="Dispatch"/>
+            </handler>
+             <handler name="SOAPActionBasedDispatcher"
+                     class="axis2_engine">
+                <order phase="Dispatch"/>
+            </handler>
+             <handler name="SOAPMessageBodyBasedDispatcher"
+                     class="axis2_engine">
+                <order phase="Dispatch"/>
+            </handler>
+        </phase>
+        <phase name="PostDispatch">
+             <handler name="DispatchPostConditionsEvaluator"
+                     class="axis2_engine">
+                <order phase="PostDispatch"/>
+            </handler>
+            <handler name="InstanceDispatcher"
+                     class="axis2_engine">
+                <order phase="PostDispatch"/>
+            </handler>
+            <handler name="SOAPProcessingModelChecker"
+                     class="axis2_engine">
+                <order phase="PostDispatch"/>
+            </handler>
+        </phase>
+        <!--  System pre defined phases       -->
+        <!--   After Postdispatch phase module author or or service author can 
add any phase he want      -->
+        <!--phase name="userphase1"/-->
+        <phase name="RMPhase"/>
+    </phaseOrder>
+    <phaseOrder type="outflow">
+        <!--      user can add his own phases to this area  -->
+           <phase name="RMPhase"/>
+        <!--phase name="userphase1"/-->
+        <!--system predefined phase-->
+        <!--these phase will run irrespective of the service-->
+        <!--phase name="PolicyDetermination"/-->
+        <!--phase name="MessageOut"/-->
+    </phaseOrder>
+    <phaseOrder type="INfaultflow">
+        <!--      user can add his own phases to this area  -->
+        <!--phase name="userphase1"/-->
+           <phase name="RMPhase"/>
+    </phaseOrder>
+    <phaseOrder type="Outfaultflow">
+        <!--      user can add his own phases to this area  -->
+        <phase name="RMPhase"/>
+        <phase name="MessageOut"/>
+        <!--phase name="userphase1"/-->
+        <!--phase name="PolicyDetermination"/-->
+    </phaseOrder>
+
+In the services xml file for the service which require RM enabled
+add the entry
+ <module ref="sandesha2"/>
+If you need all services in the engine RM enabled add the above entry into
+axis2.xml.
+
+You can use samples in the samples folder for testing.
+
+Note: Sandesha2 has two main storage mechanisms call inmemory and persistent. 
+      By default sandesha2 use the sqlite as the persistent storage. You can
+      change this to inmemory by changing the entry in the 
sandesha2_constants.h
+      file.
+        #define SANDESHA2_DEFAULT_STORAGE_MGR "persistent"
+
+        You must have sqlite3.h in sandesha2 include directory.
+        When compiling it statically link with sqlite library. So make sure 
you have
+        src/core/libsqlite3.a.
+        Above configurations regarding sqlite may be refined before the 
release.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to