Author: ruwan
Date: Sun Jun 21 03:48:04 2009
New Revision: 39512
URL: http://wso2.org/svn/browse/wso2?view=rev&revision=39512

Log:
Cleanup


Modified:
   branches/esb/java/2.1/product/modules/distribution/src/main/conf/axis2.xml

Modified: 
branches/esb/java/2.1/product/modules/distribution/src/main/conf/axis2.xml
URL: 
http://wso2.org/svn/browse/wso2/branches/esb/java/2.1/product/modules/distribution/src/main/conf/axis2.xml?rev=39512&r1=39511&r2=39512&view=diff
==============================================================================
--- branches/esb/java/2.1/product/modules/distribution/src/main/conf/axis2.xml  
(original)
+++ branches/esb/java/2.1/product/modules/distribution/src/main/conf/axis2.xml  
Sun Jun 21 03:48:04 2009
@@ -1,3 +1,4 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <!--
   ~  Copyright (c) 2005-2008, WSO2 Inc. (http://www.wso2.org) All Rights 
Reserved.
   ~
@@ -46,22 +47,19 @@
     <!-- Sandesha2 persistance storage manager -->
     <parameter name="Sandesha2StorageManager" 
locked="false">inmemory</parameter>
 
-    <!-- Following parameter will set the proper context path for invocations. 
All the endpoints -->
-    <!-- will have a common context root which can be configured using the 
following parameter -->
-    <parameter name="contextRoot" locked="false">/</parameter>
-
     <!-- Our HTTP endpoints can handle both REST and SOAP under the following 
service path. In -->
     <!-- case of a servlet container, if you change this you have to manually 
change the -->
     <!-- settings of your servlet container to map this context path to proper 
Axis2 servlets -->
     <parameter name="servicePath" locked="false">services</parameter>
 
     <!-- User agent and the server details to be used in the http 
communication -->
-    <parameter name="userAgent" locked="true">WSO2-ESB-v2.0</parameter>
-    <parameter name="server" locked="true">WSO2-ESB-v2.0</parameter>
+    <parameter name="userAgent" locked="true">WSO2-ESB-v2.1</parameter>
+    <parameter name="server" locked="true">WSO2-ESB-v2.1</parameter>
 
     <!-- During a fault, stacktrace can be sent with the fault message. The 
following flag -->
     <!-- will control that behaviour -->
     <parameter name="sendStacktraceDetailsWithFaults" 
locked="false">false</parameter>
+    
     <!-- If there aren't any information available to find out the fault 
reason, we set the -->
     <!-- message of the expcetion as the faultreason/Reason. But when a fault 
is thrown from -->
     <!-- a service or some where, it will be wrapped by different levels. Due 
to this the -->

_______________________________________________
Esb-java-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev

Reply via email to