commit 76ff05432938624b5107d7791b1eeecd5f91eb4e
author Vanjikumaran <vanjikumaran@gmail.com> Thu Apr 02 09:40:59 2020 -0700
committer GitHub <noreply@github.com> Thu Apr 02 09:40:59 2020 -0700
tree dc2c6838edf4f03dde14445ee12c1db58147d93d
parent 2d0885ce209f4090cd4c265da55e4d35ab62551f
parent 29e59964608e5f450fb0a5a6af09e769547d301f

Merge pull request #35 from shafreenAnfar/refactor2

Fix the typo in the class name

modules/documentation/src/site/xdoc/userguide/samples/sample705.xml

diff --git a/modules/documentation/src/site/xdoc/userguide/samples/sample705.xml b/modules/documentation/src/site/xdoc/userguide/samples/sample705.xml
index 8df6daf..69ec78e 100644
--- a/modules/documentation/src/site/xdoc/userguide/samples/sample705.xml
+++ b/modules/documentation/src/site/xdoc/userguide/samples/sample705.xml
@@ -60,13 +60,18 @@
                 <parameter name="interval">10000</parameter>
                 <parameter name="max.deliver.attempts">3</parameter>
                 <parameter name="max.deliver.drop">true</parameter>
+                <parameter name="retry.http.status.codes">500, 504</parameter>
                 </messageProcessor>
                 </definitions>
             </div>
             <subsection name="Objective">
                 <p>
-                    Introduction to Synapse Scheduled Message Forwarding Processor with advance parameters (max deliver
-                    attempt and drop the message after max deliver attempt)
+                    Introduction to Synapse Scheduled Message Forwarding Processor with following advance parameters
+                    <ul>
+                        <li>max.deliver.attempts</li>
+                        <li>max.deliver.drop</li>
+                        <li>retry.http.status.codes</li>
+                    </ul>
                 </p>
             </subsection>
             <subsection name="Pre-requisites">
@@ -98,6 +103,13 @@
                     "max.deliver.drop" parameter would have no effect when no value is specified for the Maximum Delivery Attempts parameter.
                     If this parameter is disabled, the undeliverable message will not be dropped and the message processor will be deactivated.
                 </p>
+                <p>
+                    Message Forwarding Processor by default do not retry for application level failures. It only retries by default when
+                    there is a network level failure. But if the user wants retry based on the application level failures, user can use
+                    "retry.http.status.codes" configuration to do so. Please note that in this context application level failures refers to
+                    HTTP error responses. For instance, in the above example Message Forwarding Processor retries not only for transport
+                    level failures but also for application level failures such as Internal Server Error (500) and Gateway timeout (504).
+                </p>
             </subsection>
         </section>
         <p>