This is an automated email from the ASF dual-hosted git repository.
pascalschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new fdb26f7 Scheduler Component: fix errors in documentation
fdb26f7 is described below
commit fdb26f7e4c6276dd26da8b35ca30a7a2b6b7dadb
Author: Pascal Schumacher <pascalschumac...@gmx.net>
AuthorDate: Wed May 2 20:44:29 2018 +0200
Scheduler Component: fix errors in documentation
---
camel-core/src/main/docs/scheduler-component.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/camel-core/src/main/docs/scheduler-component.adoc
b/camel-core/src/main/docs/scheduler-component.adoc
index 91d7b26..65b56f8 100644
--- a/camel-core/src/main/docs/scheduler-component.adoc
+++ b/camel-core/src/main/docs/scheduler-component.adoc
@@ -19,7 +19,7 @@ scheduler:name[?options]
----
Where `name` is the name of the scheduler, which is created and shared
-across endpoints. So if you use the same name for all your timer
+across endpoints. So if you use the same name for all your scheduler
endpoints, only one scheduler thread pool and thread will be used - but
you can configure the thread pool to allow more concurrent threads.
@@ -122,7 +122,7 @@ To set up a route that generates an event every 60 seconds:
[source,java]
----
-from("scheduler://foo?period=60s").to("bean:myBean?method=someMethodName");
+from("scheduler://foo?delay=60s").to("bean:myBean?method=someMethodName");
----
The above route will generate an event and then invoke the
@@ -134,7 +134,7 @@ And the route in Spring DSL:
[source,xml]
----
<route>
- <from uri="scheduler://foo?period=60s"/>
+ <from uri="scheduler://foo?delay=60s"/>
<to uri="bean:myBean?method=someMethodName"/>
</route>
----
--
To stop receiving notification emails like this one, please contact
pascalschumac...@apache.org.
