> -----Original Message----- > From: Mark E. Zawadzki [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 01, 2002 11:18 AM > To: [EMAIL PROTECTED] > Subject: Re: Help! Patching compiled code not taking in Tomcat server > > A red herring. > The setting should not matter if you have restarted. Reloadable set > to true will allow you, under certain circumstances to reload your > servlet w/o restarting. IMSM, this is done through the Tomcat > management API.
I disagree that it's a red herring. You're right that it shouldn't matter if one has restarted, but the point is that you want to be able to install new code *without* restarting. (This is probably not something you want to do in production, but it can be a great time saver during development.) I think you're right about the "under certain circumstances" part, so some people might not find this as beneficial as others, depending on which portions of code are being updated (e.g. as I said in a previous post, reloading should work fine if it's the servlet class itself that's been updated, but I'm not sure how it works if it's some auxiiliary class or jar that's been updated). > --- Margaret Fisk <[EMAIL PROTECTED]> wrote: > > It is set to false. What does the Context path do? > > > > -----Original Message----- > > From: Nigh, Bill [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, August 01, 2002 10:36 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Help! Patching compiled code not taking in Tomcat server > > > > > > Check the server.xml file in, probably, \conf\ directory, and look for > > <Context path> tag relating to your app. Check to see if the "reloadable" > > attribute is set to "true". > > > > > > Bill Nigh > > Great Atlantic & Pacific Tea Company > > Teaconet 320-4744 > > > > > > > -----Original Message----- > > > From: Margaret Fisk [SMTP:[EMAIL PROTECTED]] > > > Sent: Thursday, August 01, 2002 1:20 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: Help! Patching compiled code not taking in Tomcat > > > server > > > > > > I'll check for that. Thanks. > > > > > > -----Original Message----- > > > From: Mark E. Zawadzki [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, August 01, 2002 10:05 AM > > > To: [EMAIL PROTECTED] > > > Subject: Re: Help! Patching compiled code not taking in Tomcat server > > > > > > > > > Well, if you started and stopped the server, and by infrence the JVM, > all > > > references to the old class have gone to the bit bucket in the sky and > you > > > should be seeing your new class - therefore the old class must be > hanging > > > around somewhere. Is it somewhere in the CLASSPATH, or did you at > anytime > > > deploy this as a .war file ? > > > --- Margaret Fisk <[EMAIL PROTECTED]> wrote: > > > > Yeah, I'm afraid I've tried the basics: > > > > > > > > 1) Stop and Start the application service > > > > 2) Delete the Tomcat work folder (I know its just JSPs compiled there, > > > > but...) > > > > 3) Restarted the whole server. > > > > > > > > Is there any place that Tomcat logs changes so I can see if it really > > > isn't > > > > seeing the file? > > > > > > > > Thanks, > > > > Margaret [ ... ] Milt Epstein Research Programmer Systems and Technology Services (STS) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
