This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 9a6f33f9fb28a02ccef3523d73d0cd0458d56f1a
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Mon Feb 26 10:35:48 2018 +0100
Added automatic generation marker to onFallback docs
---
camel-core/src/main/docs/eips/onFallback-eip.adoc | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/camel-core/src/main/docs/eips/onFallback-eip.adoc
b/camel-core/src/main/docs/eips/onFallback-eip.adoc
index 13c9309..4117703 100644
--- a/camel-core/src/main/docs/eips/onFallback-eip.adoc
+++ b/camel-core/src/main/docs/eips/onFallback-eip.adoc
@@ -5,6 +5,19 @@ If you are using *onFallback* then that is intended to be
local processing only
Configuring Hystrix Example
Hystrix has many options as listed in the table above. For example to set a
higher timeout to *5* seconds, and also let the circuit breaker wait *10*
seconds before attempting a request again when the state was tripped to be open.
+== Options
+
+// eip options: START
+The On Fallback EIP supports 1 options which are listed below:
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *fallbackViaNetwork* | Whether the fallback goes over the network. If the
fallback will go over the network it is another possible point of failure and
so it also needs to be wrapped by a HystrixCommand. It is important to execute
the fallback command on a separate thread-pool, otherwise if the main command
were to become latent and fill the thread-pool this would prevent the fallback
from running if the two commands share the same pool. | false | Boolean
+|===
+// eip options: END
+
[source,java]
----
from("direct:start")
@@ -65,4 +78,4 @@ You can also configure Hystrix globally and then refer to
that configuration:
<to uri="mock:result"/>
</route>
</camelContext>
-----
\ No newline at end of file
+----
--
To stop receiving notification emails like this one, please contact
acosent...@apache.org.
