Kevin,
Thanks again.
I figured it out. Finally!
Here was my problem: I had lots of extraneous paths in the "Application Server Classpath", which all get loaded AHEAD of the Application Server API classes.
That was the problem I think. Something I was loading AHEAD of the Application Server API was probably causing it to malfunction.
I cleaned that up, left only the appserver\classes.zip file.
Then I put all my path info in User Libpath, and now it seems to work fine.
JSPs are finally cooperating again!
Thanks for your tip on OrionServer -- I will definitely check it out.
Mike
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 03, 2000 6:34 PM
To: Mike Herron
Subject: RE: Why do we have to restart after every change to a JSP?
Hi,
I am sorry, I haven't a clue as to HOW to get the classloaders working
properly. However, since JSP is write once, run anywhere, why not try a
"different" server for development, and move it over to WebSphere when its
working. We use IIS/JRUN (unfortanately) for our production site, but I
always use OrionServer for development. www.orionserver.com. Its a 100%
application server with EJB 1.1, Servlet 2.2, JSP 1.1 JNI 1.1 etc support.
ITs very easy to set up. You can just shut down WebSphere, run orion.jar
(java -j orion.jar I think it is) and your all set. You do have to set the
/orion/config/server.xml to your "root" web dir and copy 3 .xml files into
it and set those, which is very easy. I am happy to help you out on this.
Once its running, you can change JSP files and they should be reflected on
the next hit. Just keep in mind the browser caches pages, so sometimes you
may have to hit CTRL-REFRESH on the page to get it to reload the new page.
I wish I could help you out more. Hope this helps a bit.
Kevin Duffey
Software Engineer
[EMAIL PROTECTED]
