svn commit: r654560 - /synapse/branches/1.2/src/site/xdoc/Synapse_Samples_Setup.xml

[ru...@apache.org]

Author: ruwan
Date: Thu May  8 08:41:05 2008
New Revision: 654560

URL: http://svn.apache.org/viewvc?rev=654560&view=rev
Log:
Applying the patch from hiranya - PART II - (SYNAPSE-292)

Modified:
    synapse/branches/1.2/src/site/xdoc/Synapse_Samples_Setup.xml

Modified: synapse/branches/1.2/src/site/xdoc/Synapse_Samples_Setup.xml
URL: http://svn.apache.org/viewvc/synapse/branches/1.2/src/site/xdoc/Synapse_Samples_Setup.xml?rev=654560&r1=654559&r2=654560&view=diff
==============================================================================
--- synapse/branches/1.2/src/site/xdoc/Synapse_Samples_Setup.xml (original)
+++ synapse/branches/1.2/src/site/xdoc/Synapse_Samples_Setup.xml Thu May  8 08:41:05 2008
@@ -190,7 +190,7 @@
     <p>
       The above diagram depicts the interactions between the clients, Synapse
       and the services at a higher level. The Clients are able to send SOAP/REST
-      or POX messages over transports such as http/s or JMS with WS-Addressing,
+      or POX messages over transports such as HTTP/S or JMS with WS-Addressing,
       WS-Security or WS-Reliable messaging. They can send binary optimized
       content using MTOM or SwA or binary or plain text JMS messages. After
       mediation through Synapse, the requests are passed over to the sample
@@ -318,7 +318,7 @@
       Proxy Client Mode:
     </h4>
     <p>
-      In this mode, the client uses the 'prxurl' as a http proxy to send the
+      In this mode, the client uses the 'prxurl' as a HTTP proxy to send the
       request. Thus by setting the 'prxurl' to Synapse, the client can ensure
       that the message will reach Synapse for mediation. The client can
       optionally set a WS-Addressing EPR if required.
@@ -389,7 +389,7 @@
     <p/>
     <p>
       The sample services ship with a pre-configured Axis2 server and
-      demonstrates in-only and in-out SOAP/REST or POX messaging over http/s and
+      demonstrates in-only and in-out SOAP/REST or POX messaging over HTTP/S and
       JMS transports, using WS-Addressing, WS-Security and WS-Reliable Messaging
       and handling of binary content using MTOM and SwA.
     </p>
@@ -410,7 +410,7 @@
     <p>
       To start the Axis2 server, go to the samples/axis2Server directory and
       execute the axis2server.sh or axis2server.bat script. This starts the
-      Axis2 server with the http transport listener on port 9000 and https on
+      Axis2 server with the HTTP transport listener on port 9000 and HTTPS on
       9002 respectively. To enable JMS transport, you will need to setup and
       start a JMS provider. An ActiveMQ 4.0.1 or later JMS server on the local
       machine is supported by default, and can be easily enabled by uncommenting
@@ -547,7 +547,7 @@
     &lt;/transportSender&gt;</pre>
     <p/>
     <h2 id="fixtransport">
-      Setting up FIX Transport
+      Setting up the FIX Transport
     </h2>
     <p>
 	To run the FIX samples used in this guide you need a local Quickfix/J