Author: hiranya
Date: Tue Jul  7 02:30:04 2009
New Revision: 40928
URL: http://wso2.org/svn/browse/wso2?view=rev&revision=40928

Log:
Fixing an XML issue in the config lang doc



Modified:
   trunk/esb/java/docs/xdoc/configuration_language.xml

Modified: trunk/esb/java/docs/xdoc/configuration_language.xml
URL: 
http://wso2.org/svn/browse/wso2/trunk/esb/java/docs/xdoc/configuration_language.xml?rev=40928&r1=40927&r2=40928&view=diff
==============================================================================
--- trunk/esb/java/docs/xdoc/configuration_language.xml (original)
+++ trunk/esb/java/docs/xdoc/configuration_language.xml Tue Jul  7 02:30:04 2009
@@ -1133,26 +1133,26 @@
 <p>There are a set of predefined XPath variables when writing XPaths in the
 Synapse Configuration. Those are as follows; </p>
 <ul>
-  <li>body - The SOAP 1.1 or 1.2 body element </li>
+  <li>body - The SOAP 1.1 or 1.2 body element <br/>
   For example; expression="$body/getQuote" refers to the first getQuote element
-  in the SOAP body regardless of whether the message is SOAP-11 or SOAP-12
-  <li>header - The SOAP 1.1 or 1.2 header element </li>
+  in the SOAP body regardless of whether the message is SOAP-11 or SOAP-12</li>
+  <li>header - The SOAP 1.1 or 1.2 header element<br/>
   For example; expression="$header/wsa:To" refers to the addressing To header
-  regardless of whether this message is SOAP-11 or SOAP-12 </ul>
+  regardless of whether this message is SOAP-11 or SOAP-12</li></ul>
 
 <p>Further there are some variable prefixes defined in Synapse XPaths which can
 be usefull in writing the configurations; </p>
 <ul>
-  <li>ctx - Prefix for Synapse MessageContext properties </li>
+  <li>ctx - Prefix for Synapse MessageContext properties<br/>
   For example; expression="$ctx:RESPONSE" gives the value of the Synapse
-  message context property with name 'RESPONSE' 
-  <li>axis2 - Prefix for Axis2 MessageContext properties </li>
+  message context property with name 'RESPONSE'</li>
+  <li>axis2 - Prefix for Axis2 MessageContext properties<br/>
   For example; expression="$axis2:messageType" gives the value of the axis2
-  message context property with name 'messageType' 
-  <li>trp - Prefix for the transport headers </li>
+  message context property with name 'messageType' </li> 
+  <li>trp - Prefix for the transport headers<br/>
   For example; expression="$trp:Content-Type" gives the value of the
   'Content-Type' transport header, which is going to be the Content-Type of the
-  current message </ul>
+  current message </li></ul>
 
 <h4><a id="sequence_ref">Sequence</a> </h4>
 
@@ -1481,7 +1481,7 @@
 &lt;/dblreport&gt;</pre>
 
 <p>The dbreport mediator is very similar to the dblookup mediator, but writes
-information to a Database, using the specified insert SQL statement. </p>
+information to a Database, using the specified insert SQL statement.</p>
 
 <h3>Advanced Mediators </h3>
 

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

Reply via email to