# HG changeset patch
# User paulb
# Date 1076258113 0
# Node ID 282d1e3ef2a6731308efbd7607241bc86f407d42
# Parent  5c1f5831e95b2236c2e38ecb000536c8b2ac224c
[project @ 2004-02-08 16:35:13 by paulb]
Added a note about Webware's irritating conflict between context names and
package names.

diff -r 5c1f5831e95b -r 282d1e3ef2a6 docs/Webware/NOTES.txt
--- a/docs/Webware/NOTES.txt	Sun Feb 08 16:34:28 2004 +0000
+++ b/docs/Webware/NOTES.txt	Sun Feb 08 16:35:13 2004 +0000
@@ -16,12 +16,20 @@
 Each context must be defined in the Webware/WebKit/Configs/Application.config
 file within the 'Contexts' dictionary entry; for example:
 
-'Simple': '/home/paulb/Software/Python/WebStack/examples/Webware/SimpleContext',
+'simple': '/home/paulb/Software/Python/WebStack/examples/Webware/SimpleContext',
 
 Note that the path to the context directory must be absolute, although the
 context directory may reside within WebKit itself such that the path may then
 make use of the special %(WebKitPath)s substitution.
 
+Note also that the name of the context (eg. 'simple') must not be the same as
+the name of any other package used within the application (and possibly any
+other applications in the application server), with the only reasonable
+exception being the context package name itself (eg. 'SimpleContext').
+Otherwise, the existing package will become overridden by the contents of the
+context itself.  Therefore, given that the Simple package is used to hold the
+actual application code, it is not wise to use 'Simple' as the context name.
+
 Running the application server:
 
 Change into the WebKit directory within Webware. Then, specifying the