From 4c4b7000082d095c8d06d3f86177e5b19a55de2d Mon Sep 17 00:00:00 2001 From: Oleg Zhurakousky Date: Wed, 6 Jul 2011 11:56:40 -0400 Subject: [PATCH] INT-1959 fixed documentation around Task Scheduling and removed references to SimpleTaskScheduler --- docs/src/reference/docbook/configuration.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/src/reference/docbook/configuration.xml b/docs/src/reference/docbook/configuration.xml index fb16cde727..40deedf1ca 100644 --- a/docs/src/reference/docbook/configuration.xml +++ b/docs/src/reference/docbook/configuration.xml @@ -94,15 +94,16 @@
Configuring the Task Scheduler + In Spring Integration, the ApplicationContext plays the central role of a Message Bus, and there are only a couple configuration options to be aware of. First, you may want to control the central TaskScheduler instance. You can do so by providing a single bean with the name "taskScheduler". This is also defined as a constant: - By default Spring Integration uses the SimpleTaskScheduler implementation. That in turn - just delegates to any instance of Spring's TaskExecutor abstraction. Therefore, + By default Spring Integration relies on default Task Scheduler via Task Execution and Scheduling provided by the Spring Framework + That in turn just delegates to an instance of Spring's TaskExecutor abstraction. Therefore, it's rather trivial to supply your own configuration. The "taskScheduler" bean is then responsible for managing all pollers. The TaskScheduler will startup automatically by default. If you provide your own instance of - SimpleTaskScheduler however, you can set the 'autoStartup' property to false instead. + Task Scheduler however, you can set the 'autoStartup' property to false instead. When Polling Consumers provide an explicit task-executor reference in their configuration, the invocation of