Tomcat 5.5.4 works with kaffe

[Ryan Harris <rharris@usapoolsupply.com>]

I installed and am running apache tomcat 5.5.4 with Kaffe instead of
Sun's Non-Free Java 1.5. My Google searching found a few tips on how to
get 5.0.27 working with kaffe, and it worked on 5.5.4 also.


The only additional libraries I had to install were available in the
debian unstable packages:
	
	libjessie-java, libgnucrypto-java, and kjc

I also installed the compatibility libraries which include the JMX.JAR
from the apache tomcat binaries distribution
(jakarta-tomcat-5.5.4-compat.tar.gz).

Next I added the following environment variables to the file
bin/catalina.sh:

	JAVA_HOME=/usr/lib/kaffe

	#Change the compiler for jsps and give kaffe lots of memory
	# i don't know how much is really needed, but I set it to 500 Megs, 
	#the usual default for kaffe is 64M)

	JAVA_OPTS="-Dbuild.compiler=kjc -Xmx500M"
	
	#the gnucrypto and libjessie reside in this directory
	JSSE_HOME=/usr/share/java
	
	export JAVA_HOME JAVA_OPTS JSSE_HOME

And then I modified the following lines (near line 100-110) in
bin/catalina.sh

	# Add on extra jar files to CLASSPATH
	if [ -n "$JSSE_HOME" ]; then

		#Added these lines to replace 
		#the Sun Java Security stuff


CLASSPATH="$CLASSPATH":"$JSSE_HOME"/gnu-crypto.jar:"$JSSE_HOME"/jsse.jar:"$JSSE_HOME"/javax-crypto.jar
		CLASSPATH="$CLASSPATH":"$JSSE_HOME"/javax-security.jar


		#I Commented out this line.  Yuck. 

#CLASSPATH="$CLASSPATH":"$JSSE_HOME"/lib/jcert.jar:"$JSSE_HOME"/lib/jnet.jar:"$JSSE_HOME"/lib/jsse.jar

	fi

		#add this for the jmx dependencies from the compatibility package
		CLASSPATH="$CLASSPATH":"$CATALINA_HOME"/bin/jmx.jar
		

CLASSPATH="$CLASSPATH":"$CATALINA_HOME"/bin/bootstrap.jar:"$CATALINA_HOME"/bin/commons-logging-api.jar





Last I had to create the log folder and the temp folder in
the tomcat directory because it wouldn't do it on its own...
I did something like this....

mkdir /var/log/tomcat5.5.4

ln -s /var/log/tomcat5.5.4 /usr/local/share/tomcat5.5.4/logs

mkdir /usr/local/share/tomcat5.5.4/temp



Then all I had to do was execute the startup.sh script in the bin
directory...   and it worked