#
# ADOBE SYSTEMS INCORPORATED
# Copyright 2002 Adobe Systems Incorporated. All Rights Reserved.
#
# NOTICE:  Notwithstanding the terms of the Adobe GoLive End User 
# License Agreement, Adobe permits you to reproduce and distribute this 
# file only as an integrated part of a web site created with Adobe 
# GoLive software and only for the purpose of enabling your client to 
# display their web site. All other terms of the Adobe license 
# agreement remain in effect.
#

The support classes for JSP sites live here, as *.java source files,
and in ../lib/gl.jar as compiled classes.
If you modify existing Java source files, or add new source files,
you need to follow these steps:
	(1) stop the web application or JSP container
	(2) rebuild gl.jar so that its compiled classes are built
		from your modified/new source files
	(3) restart the web application or JSP container

Additionally, before you compile you need to verify that the Java
installation is (at minimum) JDK version 1.2.2.
On UNIX systems (UNIX/Linux/MacOS X) you can type to a shell prompt
	/path-to-java-installation/bin/java -version
On Windows you can type to a command prompt
	driveletter:\path-to-java-installation\bin\java -version


(1) stop the web application or JSP container
With tomcat 3.2.x, you can use the admin page, if it's been set up,
to remove the web application.  Otherwise, just shut down tomcat.
With other JSP containers, just shut down the container.
If you are running tomcat under Apache (the standard configuration
with GoLive Dynamic Content sample servers), you need to stop
Apache as well.  The sample servers provide handy "Stop web server"
and "Start web server" commands on Windows.

(2) rebuild gl.jar
In either UNIX or Windows build environments, you rebuild gl.jar by
running scripts from a command prompt (Windows) or shell (UNIX).
The current directory of the shell should be the directory in which
this file resides.

On UNIX/Linux/MacOS X and Windows (in the Cygwin UNIX emulation environment):
You need to set the following environment variables:
	JAVA_HOME	top-level directory of your Java installation
	TOMCAT_HOME	top-level directory of your JSP container
		As this variable's name suggests, this procedure has
		only been validated with the Tomcat web server.  
		You may need to manually modify the setclasspath.pl
		file if you are using a different server.
Remove ../lib/gl.jar.
Then run the "buildall.sh" script to rebuild ../lib/gl.jar.
Optionally run the "cleanall.sh" script to remove *.class files.

On Windows:
You need to set the following variables:
	JAVA_HOME	top-level directory of your Java installation
	TOMCAT_HOME	top-level directory of your JSP container
		As this variable's name suggests, this procedure has
		only been validated with the Tomcat web server.  
		You may need to manually modify the setclasspath.bat
		file if you are using a different server.
Remove ..\lib\gl.jar.
Then run the "buildall.bat" script to rebuild ..\lib\gl.jar.
Optionally run the "cleanall.bat" script to remove *.class files.

(3) restart the web application or JSP container
With tomcat 3.2.x, you can use the admin page (if it's been set up)
to add the web application.
Otherwise, just restart the JSP container.
If you are running tomcat under Apache (the standard configuration
with GoLive Dynamic Content sample servers), you need to restart
Apache as well.  The sample servers provide handy "Stop web server"
and "Start web server" commands on Windows.


Adding/deleting source files.
You may need to modify the buildall.sh/cleanall.sh (UNIX) or
buildall.bat/cleanall.bat scripts if you add or delete Java source
files.

If you add or delete files in a directory that already exists,
proceed normally: the scripts process all *.java and *.class files
in each directory that they visit.

If you create a new director