I understand, but there should be a way to load these new classes without restarting JWS. It's simply not practical to re-start the JWS every time I update my bean code. Still, if I accept to re-start during development, what happens when the system is live ? Is there a work around ? Will it work if I put the bean classes under the servlets directory ? How does JRun handle this ? > Bean class is load by default ClassLoader, it's not a cache, it's a normal > behavior only Servlet/JSP can be reload ----- Original Message ----- Subject: Changes made to bean does not reflect in JWS2.0 > Hi, > > I wrote a small bean and called it successfully from a jsp page. > Then I make some changes to the bean. > Now, if I try to load the .jsp page which uses this bean, the changes > made to the bean do not reflect. If I shutdown the Java Webserver > and restart and then load the .jsp page, the modifications to the beans > appears now. Does JWS cache the beans .class file somewhere ? > Is there a way, where I can configure JWS to see the > change in the bean class file and load it transperantly (like servlets) > ? =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JSP-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
