This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 50b33b7e00cc9d5c4da7ebe8b49308633797d4b1
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Tue Jan 14 05:31:44 2020 +0100
Regen
---
.../modules/ROOT/pages/cron-component.adoc | 6 ++---
docs/components/modules/ROOT/pages/spring.adoc | 26 ++++++++++++++++++++++
2 files changed, 29 insertions(+), 3 deletions(-)
diff --git a/docs/components/modules/ROOT/pages/cron-component.adoc
b/docs/components/modules/ROOT/pages/cron-component.adoc
index 3c5b6cd..1d337b02 100644
--- a/docs/components/modules/ROOT/pages/cron-component.adoc
+++ b/docs/components/modules/ROOT/pages/cron-component.adoc
@@ -16,7 +16,8 @@ the implementation of their choice.
The following standard Camel components support the Cron endpoints:
-- Quartz
+- Camel-quartz
+- Camel-spring
The Cron component is also supported in **Camel K**, which can use the
Kubernetes scheduler to trigger the routes when required by the cron expression.
Camel K does not require additional libraries to be plugged when using cron
expressions compatible with Kubernetes cron syntax.
@@ -40,7 +41,7 @@ Additional libraries may be needed in order to plug a
specific implementation.
// component options: START
-The Cron component supports 4 options, which are listed below.
+The Cron component supports 3 options, which are listed below.
@@ -49,7 +50,6 @@ The Cron component supports 4 options, which are listed below.
| Name | Description | Default | Type
| *cronService* (advanced) | The id of the CamelCronService to use when
multiple implementations are provided | | String
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
-| *lazyStartProducer* (producer) | Whether the producer should be started lazy
(on the first message). By starting lazy you can use this to allow CamelContext
and routes to startup in situations where a producer may otherwise fail during
starting and cause the route to fail being started. By deferring this startup
to be lazy then the startup failure can be handled during routing messages via
Camel's routing error handlers. Beware that when the first message is processed
then creating and [...]
| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the
Camel routing Error Handler, which mean any exceptions occurred while the
consumer is trying to pickup incoming messages, or the likes, will now be
processed as a message and handled by the routing Error Handler. By default the
consumer will use the org.apache.camel.spi.ExceptionHandler to deal with
exceptions, that will be logged at WARN or ERROR level and ignored. | false |
boolean
|===
// component options: END
diff --git a/docs/components/modules/ROOT/pages/spring.adoc
b/docs/components/modules/ROOT/pages/spring.adoc
index 22680a9..65a5e6c 100644
--- a/docs/components/modules/ROOT/pages/spring.adoc
+++ b/docs/components/modules/ROOT/pages/spring.adoc
@@ -380,3 +380,29 @@ Integration] for further injections.
To avoid a hung route when testing using Spring Transactions see the
note about Spring Integration Testing under Transactional Client.
+== Cron Component Support
+
+Camel-spring can be used as implementation of the Camel Cron component.
+
+
+Maven users will need to add the following additional dependency to their
`pom.xml`:
+
+[source,xml]
+------------------------------------------------------------
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-cron</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+Users can then use the cron component inside routes of their Spring or
Spring-boot application:
+
+[source,xml]
+----
+<route>
+ <from uri="cron:tab?schedule=0/1+*+*+*+*+?"/>
+ <to uri="log:info"/>
+</route>
+----
