- This topic has 20 replies, 3 voices, and was last updated 18 years ago by
.
-
Posts
-
Thanks for the quick response.
1. Yes – and it does seem to be working for the JSP page.
2. From inside MyEclipse, I assume – I have done nothing special
3. Under Java Compiler, I have Annotation Processing, Building, Errors/Warnings, javadoc and Task Tags. I don’t see anytjing about debugging symbols. On the Java Compiler page, all defaults are selected (Use default compliance settings; add variable attributes…;add line number…;add source file name…;Preserve unused …’). Only “Inline finally blocks” option is not checked.Do me a favor and shut down tomcat, remove your deployment and now go set a breakpoint in the constructor of an action you know is going to get constructed. Make a default constructor if you don’t have one with a simple System.out.println on it and set the break point there.
Now re-create the deployment, start up Tomcat and connect with your browser… does it break? If not, do you see the System.out message in the console?
No dice. Having said that, though, I can hit a breakpoint in a different project, so it must be something with this project. The output seems to indicate that the app THINKS it is loading up my Action class and ActionForm, though. The timestamp on the compiled classes in the Tomcat webapp directory is up-to-date. I’m stumped.
Okay, finally got it to work by not only removing the deployement but also deleting the deployed files from the Tomcat webapps directory. But then, when I make any changes (with project set to Build Automatically, per MyEclipse requirements when I set up the Tomcat Server), my changes are not seen by Tomcat. Even if I choose “Redeploy” – when I step into the code, the old code is still there. Is there some sort of caching going on? some setting I can change to make Tomcat pick up the latest code?
