title: Lifecycle, compilation and replacement of JSPs
body: <p>I'm having trouble to either find information about this as a whole and specifically about the placement of JSP code in tomcat.</p>
  
  <p>I have an application and develop for it. I' remotely debugging and changing code. This will not publish the code to the remote machine. So, I try to copy the JSP file over. This does not change a thing, when debugging, I can see that the debugger jumps on lines that contain no code.</p>
  
  <p>Very well. I use Lambda Probe to delete the work directory and even explicitly recompile all JSPs, including the one I wanted to change in the first place. I can view the code and even the compiled servlet code, all listing my changes. However, running the debugger again and trying to debug my changed code STILL jumps to lines as if I didn't change my code at all.</p>
  
  <p>This forces me to do a full deployment: I compile a whole WAR file, copy it to the server (it gets deployed), my program starts up, and I need about 10 minutes to get to the same point I was before.</p>
  
  <p>Where the heck does tomcat cache/deposit the code of my JSPs beside the work directory? Is it at all possible to change code "on the fly" via the debugger? I know it's possible for classes as long as I do not change the method signature, but I am helplessly struggling with the same idea in JSP files.</p>
  
  <p>Any help will be appreciated, be it links to explaining sites or explanations itself.</p>
  
  <p>Thank you.</p>