I tried to copy tools.jar to shared/lib, but I think that the JVM itself might prevent that from working,
not sure about chapter and verse though.

After perusal of the source code and comparison between 4.1.31 and 5.5.15, as well as comparing the Windows and Unix startup scripts, I am now more or less certain that the problem is in setclasspath.sh, where tools.jar is only added to the classpath if the command is 'debug' or 'javac' (which is not the case). I guess javac is not an option to start catalina, as I was mistakenly assuming earlier, but rather refers to the Java compiler. In essence, on Unix, you will never see tools.jar in the classpath. The Windows startup scripts on the other
hand, will always have tools.jar in the classpath - hence the discrepency.

I will open a bug for this, and as a workaround remove the check in setclasspath.sh for my own needs.

  Martin

Markus Schönhaber wrote:
Martin Schulz wrote:
My webapps needs to access the javac compiler classes from tools.jar.

This appears to work on dev environment on Windows, but it doesn't
in a deployment environment:
Solaris 9
JDK 1.5.0_06

The app hits a java.lang.ClassNotFoundException: com.sun.tools.javac.Main

According to the documentation, tools.jar should always be in the
class path:
http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html

If I insert an
echo $CLASSPATH
into catalina.sh on Linux, I see that tools.jar isn't included. Maybe the docs are not right (anymore?).

Looking at the startup scripts (I think I saw it in the doumentation too
somewhere) there is a 'javac' option (in catalina.sh), which appears
to be in some state of disrepair.  At least the order of arguments
passed from startup.sh does not match how catalina.sh looks at the args,
nor does catalina.sh actually consume the 'javac', or evaluate it
as a valid command.

I guess I'm confused at this stage as to what to believe and how to
proceed.

How about copying tools.jar to commons/lib?

Regards
  mks

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to