From 136c27aff3dd717e75d2b8427771875c09c8a9d8 Mon Sep 17 00:00:00 2001 From: Ben Alex Date: Thu, 29 Apr 2004 02:13:00 +0000 Subject: [PATCH] Corrected welcome page to display appropriate information depending on WAR being used. --- samples/contacts/war/WEB-INF/jsp/hello.jsp | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/samples/contacts/war/WEB-INF/jsp/hello.jsp b/samples/contacts/war/WEB-INF/jsp/hello.jsp index 12a0a7a5eb..a532b4b1c1 100644 --- a/samples/contacts/war/WEB-INF/jsp/hello.jsp +++ b/samples/contacts/war/WEB-INF/jsp/hello.jsp @@ -7,11 +7,18 @@

This is a very simple application to demonstrate the Acegi Security System for Spring. The application manages contacts, partitioned based on the user that owns them. Users may only manage their own contacts, and only users with ROLE_SUPERVISOR -are allowed to delete their contacts. The application automatically extracts -the principal from the web container (which should be configured with a -suitable Acegi Security System for Spring adapter). It also demonstrates how to configure +are allowed to delete their contacts. It also demonstrates how to configure server-side secure objects so they can only be accessed via a public facade. +

If you deployed the contacts-container-adapter.war file, the application +automatically extracts the principal from the web container (which should be +configured with a suitable Acegi Security System for Spring adapter). If +you're using the standard contacts.war file, the application is entirely +self-contained and you don't need to do anything special with your web +container. If you're using the contacts-cas.war file, please review the +setup in samples/contacts/etc/cas/applicationContext.xml for your CAS server +and if necessary rebuild using the Contacts application's build.xml. +

This application also demonstrates a public method, which is used to select the random contact that is shown below: