src-spring-framework

Spring Framework

Chris Beams 53673d6c59 Support initial delay attribute for scheduled tasks java.util.concurrent's ScheduledExecutorService and its #schedule* methods allow for an 'initialDelay' parameter in milliseconds. Similarly, Spring's TaskExecutor abstraction allows for a concrete 'startTime' expressed as a Date. However, Spring's <task:scheduled> XML element and @Scheduled annotation have, to date, not allowed for an initial delay parameter that can be propagated down to the underlying TaskScheduler/ScheduledExecutorService. This commit introduces initial-delay and #initialDelay attributes to task:scheduled and @Scheduled respectively, both indicating the number of milliseconds to wait before the first invocation of the method in question. Specifying a delay in this fashion is only valid in conjunction with fixed-rate and fixed-delay tasks (i.e. not with cron or trigger tasks). The principal changes required to support these new attributes lie in ScheduledTaskRegistrar, which previously supported registration of tasks in the form of a Runnable and a Long parameter indicating (in the case of fixed-rate and fixed-delay tasks), the interval with which the task should be executed. In order to accommodate a third (and optional) 'initialDelay' parameter, the IntervalTask class has been added as a holder for the Runnable to be executed, the interval in which to run it, and the optional initial delay. For symmetry, a TriggerTask and CronTask have also been added, the latter subclassing the former. And a 'Task' class has been added as a common ancestor for all the above. One oddity of the implementation is in the naming of the new setters in ScheduledTaskRegistrar. Prior to this commit, the setters were named #setFixedDelayTasks, #setFixedRateTasks, etc, each accepting a Map<Runnable, long>. In adding new setters for each task type, each accepting a List<IntervalTask>, List<CronTask> etc, naturally the approach would be to use method overloading and to introduce methods of the same name but with differing parameter types. Unfortunately however, Spring does not support injection against overloaded methods (due to fundamental limitations of the underlying JDK Introspector). This is not a problem when working with the ScheduledTaskRegistrar directly, e.g. from within a @Configuration class that implements SchedulingConfigurer, but is a problem from the point of view of the ScheduledTasksBeanDefinitionParser which parses the <task:scheduled> element - here the ScheduledTaskRegistrar is treated as a Spring bean and is thus subject to these limitations. The solution to this problem was simply to avoid overloading altogether, thus the naming of the new methods ending in "List", e.g. #setFixedDelayTasksList, etc. These methods exist primarily for use by the BeanDefinitionParser and are not really intended for use by application developers. The Javadoc for each of the new methods makes note of this. Issue: SPR-7022		13 years ago
.settings/gradle	…
gradle/wrapper	…
spring-aop/src	Support executor qualification with @Async#value	13 years ago
spring-asm/src	…
spring-aspects	Support executor qualification with @Async#value	13 years ago
spring-beans/src	Refactor and deprecate TransactionAspectUtils	13 years ago
spring-context	Support initial delay attribute for scheduled tasks	13 years ago
spring-context-support/src	…
spring-core/src	…
spring-expression	…
spring-instrument/src	…
spring-instrument-tomcat/src	…
spring-jdbc/src	…
spring-jms/src	…
spring-orm/src	…
spring-oxm	…
spring-struts/src	…
spring-test	Refactor and deprecate TransactionAspectUtils	13 years ago
spring-tx/src	Refactor and deprecate TransactionAspectUtils	13 years ago
spring-web/src	Add convenient WebAppInitializer base classes	13 years ago
spring-webmvc/src	Add convenient WebAppInitializer base classes	13 years ago
spring-webmvc-portlet/src	…
src	Support initial delay attribute for scheduled tasks	13 years ago
.gitignore	…
README.md	…
build.gradle	…
gradle.properties	…
gradlew	…
gradlew.bat	…
import-into-eclipse.sh	…
import-into-idea.md	…
publish-maven.gradle	…
settings.gradle	…

README.md

Spring Framework

The Spring Framework provides a comprehensive programming and configuration model for modern Java-based enterprise applications - on any kind of deployment platform. A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

The framework also serves as the foundation for Spring Integration, Spring Batch and the rest of the Spring family of projects. Browse the repositories under the SpringSource organization on GitHub for a full list.

.NET and Python variants are available as well.

Downloading artifacts

Instructions on downloading Spring artifacts via Maven and other build systems are available via the project wiki.

Documentation

See the current Javadoc and Reference docs.

Getting support

Check out the Spring forums and the Spring tag on StackOverflow. Commercial support is available too.

Issue Tracking

Spring's JIRA issue tracker can be found here. Think you've found a bug? Please consider submitting a reproduction project via the spring-framework-issues repository. The readme provides simple step-by-step instructions.

Building from source

The Spring Framework uses a Gradle-based build system. In the instructions below, ./gradlew is invoked from the root of the source tree and serves as a cross-platform, self-contained bootstrap mechanism for the build. The only prerequisites are git and JDK 1.6+.

check out sources

git clone git://github.com/SpringSource/spring-framework.git

compile and test, build all jars, distribution zips and docs

./gradlew build

install all spring-* jars into your local Maven cache

./gradlew install

import sources into your IDE

Run ./import-into-eclipse.sh or read import-into-idea.md as appropriate.

... and discover more commands with ./gradlew tasks. See also the Gradle build and release FAQ.

Contributing

Pull requests are welcome; see the contributor guidelines.

Staying in touch

Follow @springframework and its team members on Twitter. In-depth articles can be found at the SpringSource team blog, and releases are announced via our news feed.

License

The Spring Framework is released under version 2.0 of the Apache License.