diff --git a/spring-framework-reference/src/aop.xml b/spring-framework-reference/src/aop.xml index 62bf969ee4..20499a289b 100644 --- a/spring-framework-reference/src/aop.xml +++ b/spring-framework-reference/src/aop.xml @@ -2959,6 +2959,16 @@ public class Account { </bean> + + Do not activate @Configurable + processing through the bean configurer aspect unless you really + mean to rely on its semantics at runtime. In particular, make sure + that you do not use @Configurable + on bean classes which are registered as regular Spring beans with + the container: You would get double initialization otherwise, once + through the container and once through the aspect. + +
Unit testing <interfacename>@Configurable</interfacename> objects diff --git a/spring-framework-reference/src/scheduling.xml b/spring-framework-reference/src/scheduling.xml index 79eaad2b9c..9042f924b2 100644 --- a/spring-framework-reference/src/scheduling.xml +++ b/spring-framework-reference/src/scheduling.xml @@ -553,6 +553,17 @@ public void doSomething() { and must not expect any arguments. If the method needs to interact with other objects from the Application Context, then those would typically have been provided through dependency injection. + + + Make sure that you are not initializing multiple instances + of the same @Scheduled annotation class at runtime, unless you do + want to schedule callbacks to each such instance. Related to this, + make sure that you do not use @Configurable on bean classes which + are annotated with @Scheduled and registered as regular Spring beans + with the container: You would get double initialization otherwise, + once through the container and once through the @Configurable aspect, + with the consequence of each @Scheduled method being invoked twice. +