1.1 --- a/docs/JavaServlet/NOTES.txt Fri Jun 09 22:58:34 2006 +0000
1.2 +++ b/docs/JavaServlet/NOTES.txt Fri Jun 09 22:58:48 2006 +0000
1.3 @@ -1,11 +1,11 @@
1.4 Preparing the Application
1.5 =========================
1.6
1.7 -Use the build.py script in the tools/JavaServlet directory to create a Web
1.8 -application directory. Then, deploy the directory in the servlet container. For
1.9 -example:
1.10 +Use the webstack_java_build.py script (installed by setup.py but also found in the
1.11 +tools/JavaServlet directory) to create a Web application directory. Then,
1.12 +deploy the directory in the servlet container. For example:
1.13
1.14 -jython tools/JavaServlet/build.py examples/JavaServlet/SimpleApp.py \
1.15 +jython webstack_java_build.py examples/JavaServlet/SimpleApp.py \
1.16 examples/Common/Simple/ \
1.17 . \
1.18 web.xml \
1.19 @@ -35,13 +35,13 @@
1.20 WebStack resource without additional configuration being performed first:
1.21
1.22 * The web.xml template should be replaced with the protected-web.xml
1.23 - template in the build.py command. This alternative template produces a
1.24 - special deployment descriptor which introduces role-based authentication for
1.25 - the application. Consequently, upon seeing that the application requires a
1.26 - user with a given role, Tomcat will prompt for the username/password details
1.27 - of a user with that role, and once such a user has been authenticated, the
1.28 - resulting user identity is then made available via the API to the
1.29 - application.
1.30 + template in the webstack_java_build.py command. This alternative template
1.31 + produces a special deployment descriptor which introduces role-based
1.32 + authentication for the application. Consequently, upon seeing that the
1.33 + application requires a user with a given role, Tomcat will prompt for the
1.34 + username/password details of a user with that role, and once such a user
1.35 + has been authenticated, the resulting user identity is then made available
1.36 + via the API to the application.
1.37
1.38 * The server.xml configuration file in Tomcat should declare the protected
1.39 application as a privileged context; for example: