Re: tomcat 4.1.18 can't start on W2K - java.endorsed.dirs is empty ?

2003-01-14 Thread Pierre Yves Monnet
Thanks, It is running fine now !! Nice to know that we need the JDK, no the JRE - Original Message - From: Jeanfrancois Arcand [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Monday, January 13, 2003 9:33 PM Subject: Re: tomcat 4.1.18 can't start on W2K

Tomcat 4.1.18 can't start

2003-01-13 Thread Pierre Yves Monnet
Hello, Here my problem : I install on a W2000 professional a J2re1.4.1, then a Tomcat 4.1.18-LE-JDK14 Tomcat don't want to start correctly. After a start, I receive on the URL the following error via a web browser : ETAT HTTP 500 Message : Description : the server meet an internal error

tomcat 4.1.18 can't start on W2K - java.endorsed.dirs is empty ?

2003-01-13 Thread Pierre Yves Monnet
Hello, Here my problem : I install on a W2000 professional a J2re1.4.1, then a Tomcat 4.1.18-LE-JDK14 Tomcat don't want to start correctly. After a start, I receive on the URL the following error via a web browser : ETAT HTTP 500 Message : Description : the server meet an internal error

Re: tomcat 4.1.18 can't start on W2K - java.endorsed.dirs is empty?

2003-01-13 Thread Jeanfrancois Arcand
The endorsed dir is used when you want to use another parser that the one included by default with JDK 1.4 (Crimson). The error you have is produced because Tomcat requires the full JDK, not only the JRE (the jsp compiler uses classes from tools.jar, which is only included with the JDK). -