On Mon, 28 Jan 2002, Michael Kastner wrote:
> Date: Mon, 28 Jan 2002 07:59:04 +0100
> From: Michael Kastner <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: Tomcat Users List <[EMAIL PROTECTED]>
> Subject: Re: Solution to sun/tools/javac/Main - Problem and some Critique
> about classpath
>
> Siram,
>
> thank you very much for your reply. I think I wasn't specific enough. To put
> my critique in a nutshell: if I set JAVA_HOME in the environment, there
> oughtn't be a need to copy tools.jar in a /lib directory of tomcat.
>
Agreed.
> There should neither be a classpath (which you explained are ignored by
> tomcat) nor should there be any script settings necessary. The setting in
> JAVA_HOME should simply be sufficient to make the jdk's jars available to
> tomcat.
>
It *does* exactly for this, for thousands of users. The challenge is to
figure out why it didn't in your case. Historically, the most common
causes for this have been:
* JAVA_HOME points at an invalid location, or at a JRE instead of a JDK
* The installed JDK is not in the expected format, with tools.jar
available at "$JAVA_HOME/lib/tools.jar"
* OS permissions don't allow tools.jar to be read
Don't know what caused your problem, but you need to understand that your
case is definitely not universal.
> But that is not the case. Without copying tools.jar to
> {tomcat_root}/common/lib and/or {tomcat_root}/server/lib it's not recognized
> by tomcat and an exception is thrown. Was I clear?
>
> Sincerely
>
> Michael Kastner
Craig
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
