This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Once every blue moon (and I do mean it happens pretty rarely) I make a change to a jsp in my j2ee application and the change does not show up in my application. If I have had enough coffee, I realize oh if I just go to the work directory and delete the generated .java and .class file which Tomcat keeps for my jsp then my new jsp will be handled correctly next time someone vists that page. But sometimes, I have doubt and I say oh I must have done something else wrong in my jsp and so I do not think to go to the work directory to do this.
So my question is, what are some of the causes of Tomcat not regenerating the .java and the .class files for a jsp page? Is there anything I can do to reduce the rate from once every blue moon to 1/infinity?
It may be that you just need a little patience. Tomcat doesn't update instantaneously. It does a periodic scan. The default scan interval is fairly short, but if you're impatient, sometimes you might be outracing it.
An IDE is no substitute for an Intelligent Developer.