There was some question about whether enabling subclass proxies via
proxyTargetClass / proxy-target-class settings would break annotation-
based demarcation of joinpoints due to inability to discover those
annotations in various scenarios. The provided tests prove that in
any conceivable case, these annotations (@Transactional, at least)
are discovered in a consistent fashion, meaning that switching proxy
strategies should be transparent to the application and honor
intended annotation semantics.

Minor improvements made during the triage of SPR-8817

Issue: SPR-8838

Add reference to @EnableScheduling and <task:annotation-driven>

If no values are given, the query parameter is removed.

SPR-8082
SPR-7833
+ add support for CacheDefinitions declarations inside XML
+ more integration tests

+ introduced @CacheDefinition annotation
+ introduced meta-annotation to allow multiple @cache annotations
SPR-7833
SPR-8082

Since dynamic attributes were allowed in Spring 3, it raised the 
possibility to specify a type attribute on a number of the form tags.
Where it makes sense (see below) that attribute is now rejected
and reversely where it makes sense it is accepted.

InputTag allows types other than "text" but rejects type="radio" or 
type="checkbox" since there is a good reason for those to be used 
only in conjunction with the appropriate form library tags.

Other HTML input tags such as PasswordTag, HiddenInputTag, 
Checkbox(es)Tag and RadioBox(es)Tag check the dynamic attributes 
and reject them if they contain a type attribute since.