Thanks, I tried that before I posted the question, but I have since resolved the issue.
The problem was not in the changed .jsp page, but rather in an included one. The included page had a variable called "enum", which compiled fine under java 1.4, but it a keyword in java 1.6. When we upgraded to jdk 1.6 a few months ago, this page failed to recompile, but the previously generated .class file remained, and so the system continued working properly and passed all tests. However, when I recently changed the including .jsp page, it could not recompile because of the problem in the included page.
It took me several hours of browsing the generated .java code line by line before I saw it. I never did find any detailed compiler errors - that SUX about JSP.
Main Topics
Browse All Topics





by: MuraliKanthPosted on 2009-08-02 at 20:11:43ID: 25001693
using a good editor like eclipse should point out the compilation problems in your jsp. I dont think jsp compilation errors are logged anywhere as such. A shortcut would be open the .java file and try to place it in a editor GUI to get the compilation problems.