spring-framework

Spring Framework

Chris Beams d4123d0637 Support use of @Scheduled against JDK proxies Prior to this change, ScheduledAnnotationBeanPostProcessor found any @Scheduled methods against the ultimate targetClass for a given bean and then attempted to invoke that method against the bean instance. In cases where the bean instance was in fact a JDK proxy, this attempt would fail because the proxy is not an instance of the target class. Now SABPP still attempts to find @Scheduled methods against the target class, but subsequently checks to see if the bean is a JDK proxy, and if so attempts to find the corresponding method on the proxy itself. If it cannot be found (e.g. the @Scheduled method was declared only at the concrete class level), an appropriate exception is thrown, explaining to the users their options: (a) use proxyTargetClass=true and go with subclass proxies which won't have this problem, or (b) pull the @Scheduled method up into an interface. Issue: SPR-8651		14 years ago
..
.settings	Merge 3.1.0 development branch into trunk	15 years ago
src	Support use of @Scheduled against JDK proxies	14 years ago
.classpath	Upgrade to Hibernate Validator 4.2.0.Final	14 years ago
.project	Revert accidental changes in Eclipse/pom metadata	14 years ago
.springBeans	Remove "Feature" support introduced in 3.1 M1	15 years ago
build.xml	+ upgrade to AspectJ 1.6.8	16 years ago
context.iml	Upgrade to Hibernate Validator 4.2.0.Final	14 years ago
ivy.xml	used specific SLF4J versions for running the test suites of individual modules (fixing the Hibernate Validator 4.2 upgrade)	14 years ago
pom.xml	Upgrade to Hibernate Validator 4.2.0.Final	14 years ago
template.mf	cleanup of conversation dependencies	14 years ago