Re: Why do we have to restart after every change to a JSP?

[Daniel Macho]

Title: RE: Why do we have to restart after every change to a JSP?

Hi everybody. I have experienced both situations with Websphere 2.0: (JSP's don't reload and they do)   Some months ago I used Websphere under IIS and it didn't reload JSP's modified, even though time stamp was the correct one for files. Also, sometimes JSP's seemed to be reloaded but with unexpected behaviour (this problem has been reported to news more than once, search www.deja.com for WAS and IIS)   However I finally changed to Lotus Go Domino as Web Server, and the problem disappeared: Websphere was able to reload modified JSP's.   Moreover classes (support classes, beans and servlets) that were in the reload classpath in Websphere, never could be reloaded with IIS. This problem was fixed with the change to Lotus Domino Go.     Hope this helps.   Daniel Macho. [EMAIL PROTECTED]   ----- Mensaje original ----- De: Mike Herron Para: [EMAIL PROTECTED] Enviado: martes 4 de enero de 2000 0:24 Asunto: Re: Why do we have to restart after every change to a JSP? Kevin, Thanks for your reply. I think the problem might have something to do with the fact that we're importing classes at the top of every JSP.  These classes provide database access and some other basic functions. These classes are located in the /servlets/ directory. I think I read somewhere about the possibility that two different classloaders might be loading the classes and the compiled JSP page -- and apparently java code in a JSP page can't necessarily access classes loaded by another classloader. Do you know how I can specify that the same classloader be used, or that the external class files be loaded EVERY TIME a jsp or servlet that uses them is reloaded? Any help you could give me would be GREATLY appreciated.  I'm pulling my hair out over this!!! Frustrated, Mike [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, January 03, 2000 5:42 PM To: Mike Herron Subject: Re: Why do we have to restart after every change to a JSP? You shouldn't have to! I dont use WebSphere, but I use OrionServer or JRUN with IIS and neither one require a restart. With JSP, usually when the page is first accessed it checks the time/date stamp of the .jsp file to the .class file its compiled into. If there is a difference, it recompiles the .jsp file. This occurs every single page hit to the page..so I dont see why you would get those errors, unless your in some sort of development mode that doesnt do that. There should be some sort of setting that allows you to check for changes each page hit. Kevin Duffey Software Engineer [EMAIL PROTECTED]