From 81c9fa805fde22f8e765762829b587a49d249047 Mon Sep 17 00:00:00 2001
From: Joe Grandja <jgrandja@users.noreply.github.com>
Date: Fri, 15 Apr 2016 17:06:17 -0400
Subject: [PATCH] Fix AuthenticationPrincipalArgumentResolver xml doc

Fixes gh-3771
---
 docs/manual/src/docs/asciidoc/index.adoc | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/docs/manual/src/docs/asciidoc/index.adoc b/docs/manual/src/docs/asciidoc/index.adoc
index 0fae9a1435..ba6b2987e0 100644
--- a/docs/manual/src/docs/asciidoc/index.adoc
+++ b/docs/manual/src/docs/asciidoc/index.adoc
@@ -6576,10 +6576,13 @@ Spring Security provides `AuthenticationPrincipalArgumentResolver` which can aut
 
 [source,xml]
 ----
-<bean class="org.springframework.security.web.method.annotation.AuthenticationPrincipalArgumentResolver" />
+<mvc:annotation-driven>
+    <mvc:argument-resolvers>
+        <bean class="org.springframework.security.web.method.annotation.AuthenticationPrincipalArgumentResolver" />
+    </mvc:argument-resolvers>
+</mvc:annotation-driven>
 ----
 
-
 Once `AuthenticationPrincipalArgumentResolver` is properly configured, you can be entirely decoupled from Spring Security in your Spring MVC layer.
 
 Consider a situation where a custom `UserDetailsService` that returns an `Object` that implements `UserDetails` and your own `CustomUser` `Object`. The `CustomUser` of the currently authenticated user could be accessed using the following code: