typo in pointcut expression
Merge pull request #424 from md42/master

* pull424:
  typo in pointcut expression
Don't detect annotations on superclass in StAnMeta

Changes introduced in conjunction with issue SPR-11475 altered the
behavior of StandardAnnotationMetadata such that annotations could be
detected on superclasses, specifically in the case where the
AnnotatedElementUtils.getAllAnnotationAttributes() method is invoked to
obtain multiple annotations of the same type (on the lowest level in the
class hierarchy), as is the case for @Profile and @Conditional.

This commit partially reverts these changes as follows:

 - All methods in AnnotatedElementUtils now set the
   traverseClassHierarchy to false, thereby effectively reverting the
   changes made in commit 1d30bf83a0d6f303ce38526286b90172c3c596c6.
   Note, however, that the changes made to AnnotationUtils remain in
   place.

 - Introduced tests in AnnotationMetadataTests that verify behavior
   present in Spring Framework 4.0.2 and earlier.

 - Updated tests in AnnotatedElementUtilsTests so that they pass against
   the reverted changes (i.e., align with the behavior present in Spring
   Framework 4.0.2 and earlier).

 - Refined Javadoc in AnnotationMetadata with regard to annotations
   being "present" vs. "defined".

 - Refined Javadoc in AnnotatedTypeMetadata.

Issue: SPR-11475, SPR-11595
Improved StAX<->SAX bridge

Improved the SAX to StAX (and vice-versa) bridge exposed via StaxUtils.
The old integration had some issues with namespace declaration
attributes, brought to light in a XMLUnit upgrade.

Issue: SPR-11549
CacheAspectSupport checks Cache.get(key) once per invocation only

Issue: SPR-11592
Fixed SPR issue reference and aligned exception messages

Issue: SPR-11592
Update SockJS overview section and polish
Revise section explaining the flow of STOMP messages
Add doc section on configuration and performance

Issue: SPR-11450
Next development version
Revert "Next development version"

This reverts commit 4788875a4b627f615f7e496dd18ad222e981d34e.
AbstractApplicationEventMulticaster only caches if event type and source type are cache-safe

Issue: SPR-11606
Relaxed getElementTypeDescriptor assertion to not insist on a ResolvableType-known array

Issue: SPR-11608
Fix typo in documentation
Provide more accurate error message
Revert "Improve suffix pattern check"

This reverts commit 3474afb165b6efa1a15db87c088e0fe79353000f.

Unfortunately this change is likely to cause issues for applications
that use regular expressions in a URI variable. I think we will have
to leave at: if there are any dots in the last segment of the
request path, regardless of whether they're in a URI var or not,
the suffix pattern match is off.

Issue: SPR-11532
Maintenance version updates, excludes for overlapping dependencies (PR #499)
Correctly resolve accessors for static properties on Class

Issue: SPR-11609
Consistent PropertyAccessor method order as declared in the interface

Issue: SPR-11609
Document better ASYNC dispatch type config for Filters

Although the need to map the ASYNC dispatcher type to a Filter was
already mentioned, it wasn't very prominent and can be quite critical
in some cases. This change addresses that.

Issue: SPR-10440