Did you restart the web server after changing the classpath and moving the
.class files? Typically, a web server only reads the classpath at server
startup, so if you change it, you need to restart to get the change noticed.
--Jim Preston
-----Original Message-----
From: A mailing list about Java Server Pages specification and reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Krimm, Nik
Sent: Tuesday, August 01, 2000 11:10 AM
To: [EMAIL PROTECTED]
Subject: Re: error 404 when I run my own JSP
I am having a similar problem, just starting out with JSP. I get an error
500 - internal server error - everytime I try to
access a bean that I have made. My theory is that for some reason that JSP
is not recognizing the bean is out there, so I've adjusted the CLASSPATH in
the environmental variables, and I tried moving the .class over to where the
jsp example classes are (these examples work correctly in my browser), but
no luck. Is there any other kind of registration I need to do to let JSP
know that a bean is out there?
TIA
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
