As Craig
pointed out, I moved to Tomcat/4 beta and reloading issue is solved. Changes to
actions and action forms are refreshed automatically by Tomcat itself. A tip for
Jbuilder, instead of compiling and copying class files, just change the output
directory to ../WEB-INF/classes and JB will create correct directory structure. Thanks to all
who kindly replied, --a -----Original
Message----- hi Ali, A change in a jsp does not warrant a restart but the others do. Any
change in struts-config or an action class is not reflected otherwise. A
changed form bean will sometimes throw an exception too. Cheers, Sridhar S Real knowledge is to know the extent of one's ignorance. -----Original Message----- Hi all, I’m new in this list so please be patient. I
looked into docs and mail archives, and deja but couldn’t find a solution to
the problem. Every time I make a chance in the formbean, action, jsp, or the
strut-config.xml file, I have to stop and restart Tomcat. Is this necessary (if
yes, dang!), if not how can I correct this (making every change not requiring
restarting Tomcat)? Thanks --a |
- reloading issue Ali Ozoren
- Re: reloading issue Pramod
- RE: reloading issue Sridhar S
- Re: reloading issue Ali Ozoren
- Re: reloading issue Jean-Noel Ribette
- Re: reloading issue Maya Muchnik
- Re: reloading issue Craig R. McClanahan
- Re: reloading issue Maya Muchnik