Bug#304543: SableVM

Wed Apr 13 22:39:05 2005

Package: tomcat4
Version: 4.1.31-2
Severity: wishlist

On Apr 13, 2005, at 2:01 PM, Barry Hawkins wrote:
> Did you test anything beyond startup?  Tomcat expects a full Sun-like
> JDK layout where you specify JAVA_HOME, so I doubt you set it to use
> sablevm and it ran without issue.

Well, I browsed around http://localhost:8180/index.jsp & ran some of 
the demo sevlets & JSPs - so far so good.

I'm setting up libapache-mod-jk2 as I speak...

It's a stock installation of -

	sablevm & jikes-sablevm 1.11.1-2
	jikes 1.22-2
	tomcat4 4.1.31-2

- with -

	JAVA_HOME=/usr/lib/sablevm
	JSP_COMPILER=jikes
	TOMCAT4_SECURITY=no

JSP_COMPILER=jikes compiles some JSPs that otherwise fail - but init 
script could do -

	if [ -z "$JSP_COMPILER" -a "$JAVA_HOME" = "/usr/lib/sablevm" ]; then
		JSP_COMPILER=jikes
	fi

- like it does for kaffe & kjc

> [...] If you want to run free, I would
> recommend kaffe for now.
>
>> Perhaps JDK_DIRS in /etc/init.d/tomcat4 should include 
>> /usr/lib/sablevm
>> - & perhaps /usr/lib/fjsdk - if it worked : )
>
> JDK_DIRS only includes paths to JDKs that *work* fully, and that
> collection serves as a convenience.  Any other experimentation or a
> desire to use a specific JDK should be done by setting JAVA_HOME in
> /etc/default/tomcat4. Once we have free runtimes other than kaffe that
> support everything Tomcat needs, you can be sure that they will be 
> included.

kaffe doesn't currently work for me at all - 
http://thread.gmane.org/gmane.linux.debian.devel.java/4329

sablevm currently works at least as well : )

Sincere thanks for maintaining tomcat!

Jack