Try this article: http://www1.allaire.com/Handlers/index.cfm?ID=12019&Method=Full Beans can only be dynamically reloaded if one of the classes that uses them gets a new timestamp, and if the bean is in one of JRun's servlets directories (i.e., not in the JVM's classpath). The JRun custom class loader dynamically reloads classes stored in the servlets directories _if_ they are supporting classes of a servlet whose timestamp has just been updated. When JRun does this it destroys all loaded custom class loaders and then reloads the requested servlet plus any of its supporting classes that are also in the servlets directory. If the beans are in the classpath then they won't get dynamically reloaded, even if they are supporting classes. If you are going to change the beans frequently enough to use this feature, you can work around the supporting class issue by using the UNIX command "touch" to update the timestamp on the/a class that calls the bean. Thus you make the called servlet "new" and the old class is destroyed along with its class loader and all its supporting classes. The article explains it in full. Scott Stirling Allaire Corporation JRun: http://www.allaire.com/developer/jrunreferencedesk/ Allaire Knowledge Base: http://www1.allaire.com/Support/KnowledgeBase/SearchForm.cfm > -----Original Message----- > From: Patterson, Jeff (I.S.) [mailto:[EMAIL PROTECTED]] > > I've heard it was possible to configure JRun to automatically reload > JavaBeans when they change without having to restart the > service, but I > can't seem to figure out how to do it and I can't find it in the > documentation. If anyone has done this, would you please > tell me how??? =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". FAQs on JSP can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html
