synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From asan...@apache.org
Subject svn commit: r593056 - in /webservices/synapse/branches/1.1/src/site/resources: Synapse_Configuration_Language.html Synapse_QuickStart.html Synapse_Samples.html
Date Thu, 08 Nov 2007 08:23:18 GMT
Author: asankha
Date: Thu Nov  8 00:23:00 2007
New Revision: 593056

URL: http://svn.apache.org/viewvc?rev=593056&view=rev
Log:
doc - spelling corrections

Modified:
    webservices/synapse/branches/1.1/src/site/resources/Synapse_Configuration_Language.html
    webservices/synapse/branches/1.1/src/site/resources/Synapse_QuickStart.html
    webservices/synapse/branches/1.1/src/site/resources/Synapse_Samples.html

Modified: webservices/synapse/branches/1.1/src/site/resources/Synapse_Configuration_Language.html
URL: http://svn.apache.org/viewvc/webservices/synapse/branches/1.1/src/site/resources/Synapse_Configuration_Language.html?rev=593056&r1=593055&r2=593056&view=diff
==============================================================================
--- webservices/synapse/branches/1.1/src/site/resources/Synapse_Configuration_Language.html
(original)
+++ webservices/synapse/branches/1.1/src/site/resources/Synapse_Configuration_Language.html
Thu Nov  8 00:23:00 2007
@@ -177,7 +177,7 @@
 service. A proxy service maybe a SOAP or POX service over http/s or SOAP, POX
 or Plain Text service for other transports such as JMS and VFS - e.g. CSV
 content being its payload. Thus Synapse is able to switch between these
-message formats and transports, as well as intrduce or terminate QoS aspects
+message formats and transports, as well as introduce or terminate QoS aspects
 such as WS-Security/RM through proxy services. </p>
 
 <p></p>
@@ -229,7 +229,7 @@
    &lt;parameter name="string"&gt;text | xml&lt;/parameter&gt;*
  &lt;/registry&gt;</pre>
 
-<p>Registry entries loaded from a remote registry are cached within Synapase
+<p>Registry entries loaded from a remote registry are cached within Synapse
 as dictated by the registry, and reloaded after the cache periods expires.
 Hence it is possible to define configuration elements such as (dynamic)
 sequences and endpoints, as well as resources such as XSLT's or XSDs off the
@@ -250,7 +250,7 @@
 
 <p>An entry can be static text specified as inline text or static XML
 specified as an inline XML fragment or specified as a URL (using the src
-attribute). These local entries can overide any existing entries with the
+attribute). These local entries can override any existing entries with the
 same keys of the remote registry. </p>
 
 <p></p>
@@ -278,7 +278,7 @@
 sequence, it executes the defined error handling sequence for the current
 context - which may be specified as the 'onError' sequence for a sequence
 mediator. If a fault sequence is not specified or cannot be found through the
-registry, Synapse will create a defualt fault sequence that will perform a
+registry, Synapse will create a default fault sequence that will perform a
 default logging of the message at the log level 'full'.</p>
 
 <p>If an optional error handler sequence name is specified on any sequence
@@ -306,7 +306,7 @@
 &lt;/endpoint&gt; </pre>
 
 <p>All above endpoint types can have a name attribute. Such named endpoints
-can be reffered by other endpoints, which only contain the key attribute. For
+can be refered by other endpoints, which only contain the key attribute. For
 example if there is an endpoint named as "foo", following endpoint can be
 used in any place, where "foo" has to be used. A tracing enabled endpoint
 would generate trace information into the trace log for each message that
@@ -353,7 +353,7 @@
 <h4><a name="wsdl-endpoint">WSDL Endpoint</a></h4>
 
 <p>WSDL endpoint is an endpoint based on a WSDL document. It can extract the
-target EPR from a given WSDL. The WSDL document can be specifed either as a
+target EPR from a given WSDL. The WSDL document can be specified either as a
 URI or as an inlined definition within the configuration. The service and
 port name containing the target EPR has to be specified in service and port
 attributes respectively. enableRM, enableSec, enableAddressing,
@@ -409,7 +409,7 @@
 as the primary and all other endpoints are treated as backups. Incoming
 messages are always sent only to the primary endpoint. If the primary
 endpoint fails, next active endpoint is selected as the primary and failed
-endpoint is marked as incative. Thus it sends messages successfully as long
+endpoint is marked as inactive. Thus it sends messages successfully as long
 as there is at least one active endpoint among the listed endpoints.</p>
 <pre>&lt;failover&gt;
   &lt;endpoint .../&gt;+
@@ -707,7 +707,7 @@
   <li>custom = Only properties specified to the Log mediator</li>
 </ul>
 
-<p>A separator if defined will be used to seperate the attributes being
+<p>A separator if defined will be used to separate the attributes being
 logged. The default separator is the ',' comma.</p>
 
 <p></p>
@@ -910,7 +910,7 @@
 the message context. The DB connection used maybe looked up from an external
 DataSource or specified in-line, in which case an Apache DBCP connection pool
 is established and used. Apache DBCP connection pools support the following
-propeties:</p>
+properties:</p>
 <ul>
   <li>autocommit = true | false</li>
   <li>isolation = Connection.TRANSACTION_NONE |
@@ -1002,12 +1002,12 @@
 <p></p>
 
 <p>The Throttle mediator can be used for rate limiting as well as concurrency
-based limiting. A WS-Policy dictates the throttling configuation and may be
-specified inline or loaded from the reistry. The Throttle mediator could be
+based limiting. A WS-Policy dictates the throttling configuration and may be
+specified inline or loaded from the registry. The Throttle mediator could be
 added in the request path for rate limiting and concurrent access limitation.
 When using for concurrent access limitation, the same throttle mediator ID
 must be triggered on the response flow so that completed responses are
-deducted from the available limit. The aceeptance or rejection sequence is
+deducted from the available limit. The acceptance or rejection sequence is
 executed depending on the evaluation of the throttling policy against the
 current message.</p>
 
@@ -1042,7 +1042,7 @@
 <p>The expressions will be evaluated against the current SOAP envelope.</p>
 
 <h4><a name="cache">Cache</a></h4>
-<pre> &lt;cache (id="string")? hashGenerator="class" scope="string" timeout="mili-seconds"&gt;
+<pre> &lt;cache (id="string")? hashGenerator="class" scope="string" timeout="milliseconds"&gt;
    &lt;onCacheHit (sequence="key")?&gt;
      (mediator)+
    &lt;/onCacheHit&gt;
@@ -1070,8 +1070,8 @@
 
 <p>The &lt;clone&gt; mediator closely resembles the Message Splitter EIP and
 will split the message into number of identical messages all of which are
-identical with the clonning message and processed parallely using either the
-specified sequence or endpoint (or both). Clonning message (parent) can be
+identical with the cloning message and processed parallelly using either the
+specified sequence or endpoint (or both). Cloning message (parent) can be
 continued or dropped depending on the boolean value of the continueParent
 attribute which defaults to false and drops the parent when false. This drop
 is not a general drop, rather stop the message processing but does not closes
@@ -1094,7 +1094,7 @@
 message in to number of different messages derived from the parent message by
 finding the matching elements of the XPATH expression specified in the
 configuration. New messages will be created for each and every matching
-element and processed parallely using either the specified sequence or
+element and processed parallelly using either the specified sequence or
 endpoint or both. Parent message can be continued or dropped in the same way
 as in the clone mediator. Iterate parent drop also is a channel blocking drop
 as per in the clone mediator.</p>

Modified: webservices/synapse/branches/1.1/src/site/resources/Synapse_QuickStart.html
URL: http://svn.apache.org/viewvc/webservices/synapse/branches/1.1/src/site/resources/Synapse_QuickStart.html?rev=593056&r1=593055&r2=593056&view=diff
==============================================================================
--- webservices/synapse/branches/1.1/src/site/resources/Synapse_QuickStart.html (original)
+++ webservices/synapse/branches/1.1/src/site/resources/Synapse_QuickStart.html Thu Nov  8
00:23:00 2007
@@ -388,14 +388,13 @@
 and view the WSDL of the virtual proxy service. But in the Synapse
 configuration, such requests can be handled in anyway you like. Most obvious
 thing would be to do some processing to the message and send it to the actual
-service, probably running on a different computer. But it is not neccessary
-to always send the message to the actual service. You may list any
-combination of tasks to be performed on the messages received for the proxy
-service and terminate the flow or send some messge back to the client even
-without sending it to an actual service. Let's explore a simple proxy
-services scenario step by step to get a better feeling. As you have
-downloaded and installed Synapse in the previous section, now you can start
-directly on the sample.</p>
+service, probably running on a different computer. But it is not necessary to
+always send the message to the actual service. You may list any combination
+of tasks to be performed on the messages received for the proxy service and
+terminate the flow or send some java back to the client even without sending
+it to an actual service. Let's explore a simple proxy services scenario step
+by step to get a better feeling. As you have downloaded and installed Synapse
+in the previous section, now you can start directly on the sample.</p>
 
 <p></p>
 
@@ -470,7 +469,7 @@
 
 <p>Synapse will display a set of messages as in the previous section
 describing the steps of starting procedure. Before running the client, it is
-time to observe another feature of proxy services. That is diplaying the
+time to observe another feature of proxy services. That is displaying the
 published WSDL. Just open a web browser and point it to the address
 http://localhost:8080/soap/StockQuoteProxy?wsdl. You will see the
 sample_proxy_1.wsdl specified in the configuration but containing the correct
@@ -498,8 +497,8 @@
 <p></p>
 
 <p>This quick guide illustrates the simple use case of proxy services. Please
-refer to samples #100 and above in the Samples guide, for indepth coverage of
-more advanced use cases.</p>
+refer to samples #100 and above in the Samples guide, for in depth coverage
+of more advanced use cases.</p>
 
 <p></p>
 

Modified: webservices/synapse/branches/1.1/src/site/resources/Synapse_Samples.html
URL: http://svn.apache.org/viewvc/webservices/synapse/branches/1.1/src/site/resources/Synapse_Samples.html?rev=593056&r1=593055&r2=593056&view=diff
==============================================================================
--- webservices/synapse/branches/1.1/src/site/resources/Synapse_Samples.html (original)
+++ webservices/synapse/branches/1.1/src/site/resources/Synapse_Samples.html Thu Nov  8 00:23:00
2007
@@ -261,7 +261,7 @@
       <li><a href="#Class">Extending the mediation in java (Class
         Mediator)</a> 
         <ul>
-          <li><a href="#Sample380">Sample 380: Writting your own custom
+          <li><a href="#Sample380">Sample 380: Writing your own custom
             mediation in Java</a></li>
         </ul>
       </li>
@@ -1140,7 +1140,7 @@
 
 <p>The configuration now sets a local message context property, and forwards
 the message to 'http://localhost:9000/soap/MTOMSwASampleService' optimizing
-bindary content as MTOM. By sending this message through TCPMon you would be
+binary content as MTOM. By sending this message through TCPMon you would be
 able to see the actual message sent over the http transport if required. Thus
 during response processing, by checking the local message property Synapse
 could identify the past information about the current message context, and
@@ -1706,12 +1706,12 @@
 
 <p>Specified service and port refers to the endpoint address
 "http://localhost:9000/soap/SimpleStockQuoteService" according to the above
-WSDL. Now run the client using the below command.</p>
+WSDL. Now run the client using the following command.</p>
 <pre>ant stockquote -Dsymbol=IBM -Dmode=quote -Daddurl=http://localhost:8080</pre>
 
 <p>Client will print the quote price for IBM received from the server running
 on port 9000. Observe the Axis2 console and the Synapse console to verify
-this behavoir.</p>
+this behavior.</p>
 
 <h1><a name="MessageMediationQoS">Quality of Service addition or deduction
 samples in message mediation</a></h1>
@@ -2233,7 +2233,7 @@
 response received does use WS-Security, and forwarded back to the client
 without any modification. You should note that this wont be a security hole
 because the message inside synapse is signed and encrypted and can only be
-forwarded to a secure service to be usefull.</p>
+forwarded to a secure service to be useful.</p>
 
 <h1><a name="ProxyServiceQoS">QoS addition and deduction for service
 mediation (proxy) samples</a></h1>
@@ -2931,10 +2931,10 @@
 value, if the count is not present as in this sample this task will run
 forever.</p>
 
-<p>One can write his own task class implmenting the
+<p>One can write his own task class implementing the
 org.apache.synapse.startup.Task interface and implementing the execute method
-to do the task. For this particualr sample we have used the MessageInjector
-which just injects a message specified in to the synapse enviorenemnt.</p>
+to do the task. For this particular sample we have used the MessageInjector
+which just injects a message specified in to the synapse environment.</p>
 
 <h1><a name="AdvancedMediation">Advanced mediations with advanced
 mediators</a></h1>
@@ -3098,7 +3098,7 @@
 
 <p></p>
 
-<p>This example shows how an inline Javascript mediator script could access
+<p>This example shows how an inline JavaScript mediator script could access
 the Synapse message context API to set its 'To' EPR and to set a custom
 property to mark it as a response. Execute the stock quote client, and you
 will receive the response "99.9" as the last sale price as per the above
@@ -3799,12 +3799,13 @@
 
 <h2><a name="Class">Extending the mediation in java (Class Mediator)</a></h2>
 
-<p>Class mediator can be used to write your own custom mediation in java and you have
the access to
-the SynapseMessageContext and all the synapse API in there. This is a good extending mechanism
-within synapse to extend it's functionality. This class can contain fields which can be fead
by the
-configuration at runtime</p>
+<p>Class mediator can be used to write your own custom mediation in Java and
+you have access to the SynapseMessageContext and all the Synapse API in
+there. This is a useful extension mechanism within Synapse to extend its
+functionality. This class can contain fields for which you can assign values
+at runtime through the configuration.</p>
 
-<h2><a name="Sample380">Sample 380: Writting your own custom mediation in
+<h2><a name="Sample380">Sample 380: Writing your own custom mediation in
 Java</a></h2>
 <pre>&lt;definitions xmlns="http://ws.apache.org/ns/synapse"&gt;
 
@@ -3955,8 +3956,8 @@
 All the details of the message including the SOAP headers, SOAP body and
 properties of the context hierarchy can be accessed from the message context.
 In this sample, the body of the message is retrieved and the discount
-percentage is substracted from the quote price. If the quote request number
-is less than the number specified in the "bonusFor" property in the
+percentage is subtracted from the quote price. If the quote request number is
+less than the number specified in the "bonusFor" property in the
 configuration, a special discount is given.</p>
 
 <p></p>
@@ -4136,7 +4137,7 @@
 &lt;/definitions&gt;</pre>
 
 <p><b><strong>Objective: Demonstrate the use of Iterate mediator to split
the
-messages in to parts and process them asynchronously and then aggreagate the
+messages in to parts and process them asynchronously and then aggregate the
 responses coming in to synapse</strong></b></p>
 
 <p><strong>Prerequisites:</strong>Deploy the SimpleStockQuoteService in
@@ -4145,7 +4146,7 @@
 <p>Start Synapse with the sample configuration 400 (i.e. synapse -sample
 400).</p>
 
-<p>In this sample, the message sent to synapse has embeded with a number of
+<p>In this sample, the message sent to synapse has embedded with a number of
 elements of the same type in one message. When synapse received this message
 it will iterate through those elements and then sent to the specified
 endpoint. When all the responses appear in to synapse then those messages
@@ -4166,10 +4167,10 @@
 
 <p>Cached mediator can be used to utilize the network bandwidth, to protect
 the backend service from being loaded with the same type of requests like
-browser refresh and also to speed up the execution of the webservice. This
-mediator should be used with sence, because it is not applicable for each and
-every services (for example services with dynamic responses for a particular
-release)</p>
+browser refresh actions and also to speed up the execution of the web
+service. This mediator should be used with sence, because it is not
+applicable for each and every service (for example services with dynamic
+responses for a particular release)</p>
 
 <h2><a name="Sample420">Sample 420: Simple cache implemented on synapse for
 the actual service</a></h2>
@@ -4212,11 +4213,11 @@
 <p>To observe this behaviour, invoke the client as follows. </p>
 <pre>ant stockquote -Dtrpurl=http://localhost:8080/</pre>
 
-<p>You could notice that if you send more than one requests withing 20
-seconds only the first request is forwarded to the actual service, and the
-rest of the requests will be served by the cache inside syanpse. You could
-observe this by looking at the priting line of the axis2 server, as well as
-by observing a constant rate as the response to the client instead of the
-random rate, which changes by each and every 20 seconds.</p>
+<p>You could notice that if you send more than one requests within 20 seconds
+only the first request is forwarded to the actual service, and the rest of
+the requests will be served by the cache inside Synapse. You could observe
+this by looking at the printed line of the axis2 server, as well as by
+observing a constant rate as the response to the client instead of the random
+rate, which changes by each and every 20 seconds.</p>
 </body>
 </html>



---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org


Mime
View raw message