corresponding element: • (Groovy) • (BeanShell) • std/> (JSR-223, e.g. with JRuby) The exact attributes and child elements that are available for configuration excuse the “jumping-through-hoops-to-pause-the-execution” shenanigans in this next slice of code.) The System.in.read() call is only there so that the execution of the program pauses while you (the developer file so that the refresh triggers on the dynamic-language-backed bean when the program resumes execution. The following listing shows this sample application: 28 import org.springframework.context.ApplicationContext;

corresponding element: • (Groovy) • (BeanShell) • std/> (JSR-223, e.g. with JRuby) The exact attributes and child elements that are available for configuration excuse the “jumping-through-hoops-to-pause-the-execution” shenanigans in this next slice of code.) The System.in.read() call is only there so that the execution of the program pauses while you (the developer file so that the refresh triggers on the dynamic-language-backed bean when the program resumes execution. The following listing shows this sample application: 28 import org.springframework.context.ApplicationContext;

resources Creating email content using a templating library A Velocity-based example 34. Task Execution and Scheduling Introduction The Spring TaskExecutor abstraction TaskExecutor types Using a TaskExecutor implementations TaskScheduler implementations Annotation Support for Scheduling and Asynchronous Execution Enable scheduling annotations The @Scheduled Annotation The @Async Annotation Executor qualification TestTransaction API. See the section called “Programmatic transaction management” for details. SQL script execution can now be configured declaratively via the new @Sql and @SqlConfig annotations on a per-class or

resources Creating email content using a templating library A Velocity-based example 34. Task Execution and Scheduling Introduction The Spring TaskExecutor abstraction TaskExecutor types Using a TaskExecutor implementations TaskScheduler implementations Annotation Support for Scheduling and Asynchronous Execution Enable scheduling annotations The @Scheduled annotation The @Async annotation Executor qualification TestTransaction API. See the section called “Programmatic transaction management” for details. SQL script execution can now be configured declaratively via the new @Sql and @SqlConfig annotations on a per-class or

Velocity-based example ....................................................................... 748 34. Task Execution and Scheduling ................................................................................ ................................ 755 34.4. Annotation Support for Scheduling and Asynchronous Execution ....................... 755 Enable scheduling annotations ..................................... API. • See the section called “Programmatic transaction management” for details. • SQL script execution can now be configured declaratively via the new @Sql and @SqlConfig annotations on a per-class or

Velocity-based example ....................................................................... 758 34. Task Execution and Scheduling ................................................................................ ................................ 764 34.4. Annotation Support for Scheduling and Asynchronous Execution ....................... 764 Enable scheduling annotations ..................................... API. • See the section called “Programmatic transaction management” for details. • SQL script execution can now be configured declaratively via the new @Sql and @SqlConfig annotations on a per-class or

the Ordered interface. Here, it is the order of registration that dictates the order of execution. Note also that BeanPostProcessor instances registered programmatically are always processed point: A point during the execution of a program, such as the execution of a method or the handling of an exception. In Spring AOP, a join point always represents a method execution. 320 • Advice: Action with a pointcut expression and runs at any join point matched by the pointcut (for example, the execution of a method with a certain name). The concept of join points as matched by pointcut expressions

point: A point during the execution of a program, such as the execution of a method or the handling of an exception. In Spring AOP, a join point always represents a method execution. Join point information with a pointcut expression and runs at any join point matched by the pointcut (for example, the execution of a method with a certain name). The concept of join points as matched by pointcut expressions advice: Advice that executes before a join point, but which does not have the ability to prevent execution flow proceeding to the join point (unless it throws an exception). • After returning advice: Advice

point: A point during the execution of a program, such as the execution of a method or the handling of an exception. In Spring AOP, a join point always represents a method execution. Join point information with a pointcut expression and runs at any join point matched by the pointcut (for example, the execution of a method with a certain name). The concept of join points as matched by pointcut expressions advice: Advice that executes before a join point, but which does not have the ability to prevent execution flow proceeding to the join point (unless it throws an exception). • After returning advice: Advice

point: A point during the execution of a program, such as the execution of a method or the handling of an exception. In Spring AOP, a join point always represents a method execution. Join point information with a pointcut expression and runs at any join point matched by the pointcut (for example, the execution of a method with a certain name). The concept of join points as matched by pointcut expressions advice: Advice that executes before a join point, but which does not have the ability to prevent execution flow proceeding to the join point (unless it throws an exception). • After returning advice: Advice