From f3b30040853e5c15f325421aad26f636caf7d26a Mon Sep 17 00:00:00 2001
From: Luke Taylor <luke.taylor@springsource.com>
Date: Sat, 15 Nov 2008 06:28:01 +0000
Subject: [PATCH] Removed references to Acegi in contacts sample home page

---
 .../contacts/src/main/webapp/WEB-INF/jsp/hello.jsp   | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/samples/contacts/src/main/webapp/WEB-INF/jsp/hello.jsp b/samples/contacts/src/main/webapp/WEB-INF/jsp/hello.jsp
index 04d01e98b4..02758ef0b8 100644
--- a/samples/contacts/src/main/webapp/WEB-INF/jsp/hello.jsp
+++ b/samples/contacts/src/main/webapp/WEB-INF/jsp/hello.jsp
@@ -4,7 +4,7 @@
 <head><title>Contacts Security Demo</title></head>
 <body>
 <h1>Contacts Security Demo</h1>
-<P>Contacts demonstrates the following central Acegi Security capabilities:
+<P>Contacts demonstrates the following central Spring Security capabilities:
 <ul>
 <li><b>Role-based security</b>. Each principal is a member of certain roles,
     which are used to restrict access to certain secure objects.</li>
@@ -15,20 +15,20 @@
    layer bean has a number of secured (protected) and public (unprotected)
    methods.</li>
 <li><b>Web request security</b>. The <code>/secure</code> URI path is protected
-   by Acegi Security from principals not holding the
+   by Spring Security from principals not holding the
    <code>ROLE_USER</code> granted authority.</li>
 <li><b>Security unaware application objects</b>. None of the objects
-   are aware of the security being implemented by Acegi Security. *</li>
-<li><b>Security taglib usage</b>. All of the JSPs use Acegi Security's
+   are aware of the security being implemented by Spring Security. *</li>
+<li><b>Security taglib usage</b>. All of the JSPs use Spring Security's
    taglib to evaluate security information. *</li>
 <li><b>Fully declarative security</b>. Every capability is configured in
-   the application context using standard Acegi Security classes. *</li>
+   the application context using standard Spring Security classes. *</li>
 <li><b>Database-sourced security data</b>. All of the user, role and ACL
    information is obtained from an in-memory JDBC-compliant database.</li>
 <li><b>Integrated form-based and BASIC authentication</b>. Any BASIC
    authentication header is detected and used for authentication. Normal
    interactive form-based authentication is used by default.</li>
-<li><b>Remember-me services</b>. Acegi Security's pluggable remember-me
+<li><b>Remember-me services</b>. Spring Security's pluggable remember-me
    strategy is demonstrated, with a corresponding checkbox on the login form.</li>
 </ul>
 
