This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Build 020503: If there are same jsps but under different diretories inside web module, and "Build all" on web module directory, there are compiling errors like this: JSP$jsp.java [9:1] duplicate class: org.apache.jsp.JSP$jsp public class JSP$jsp extends HttpJspBase { ^ JSP$jsp.java [17:1] modifier private static not allowed here private static boolean _jspx_inited = false; ^ JSP$jsp.java [9:1] org.apache.jsp.JSP$jsp should be declared abstract; it does not define _jspService() in org.apache.jasper.runtime.HttpJspBase public class JSP$jsp extends HttpJspBase { ^ 3 errors Errors compiling. It is fine if compile them separately. It is also OK to execute the web module and access each of the jsps.
This is caused by the fact that the Tomcat JSP compiler creates two servlets which are in different locations but have the same classname. When the Java compiler then compiles them, it does not handle this case. This situation does not happen when compiling JSPs one by one, because then the Java compiler, too, compiles only one page at a time. However, in the case of compiling multiple pages at a time, the Java compiler is passed all of them at once. The fix would be to call the Java compiler separately for each page, but this may require non-trivial (and controversial) changes in the Java module. The workaround is to compile pages one by one.
This should be fixed by removing the compilation feature as it is now, and replacing it with 1) the kind of tools compilation that is specified in JSP 2.0 2) a JSP validation action
Set target milestone to TBD
*** Issue 25907 has been marked as a duplicate of this issue. ***
Raising the priority to P2.
The workaround is to set the IDE integration mode to Minimal.
Requesting to waive for NetBeans 3.4. Per the bug description, the fix is non-trivial and would significantly delay the release.
I agree with the waiver.
approved waiver; keep my name in cc for release note purposes
*** Issue 26823 has been marked as a duplicate of this issue. ***
Having JSPs with the same name in different directories is absolutely common (e.g. index.jsp). As NetBeans is the best tool when developing WebApps, I would really appreciate if you can manage to integrate a sophisticated solution of the problem.
*** Issue 26961 has been marked as a duplicate of this issue. ***
Since this defect existed in FFJ4.0 it is automatically qualified for a waiver for S1S4.1.
*** Issue 33124 has been marked as a duplicate of this issue. ***
*** Issue 33911 has been marked as a duplicate of this issue. ***
*** Issue 37170 has been marked as a duplicate of this issue. ***
Fixed by removing the JSP compilation feature.
What does this mean? You can no longer compile JSPs??
JSPs are compiled by the server when they are run on the server. Instead of compiling JSPs in the IDE, you can use the "Validate" action, which is much faster and more lightweight than compilation. It catches almost all errors that compilation did. You can try this our in the NB 3.6 dev builds, available from www.netbeans.org.
I guess for 3.6 we should release note the removal of the "compile JSP" command. Chris, could you write a quick summary?
Suggested Release Notes Entry Validate JSP action replaces Compile JSP Action This version of the IDE provides a Validate action instead of a Compile action. The Validate action detects all syntax problems except for syntax errors that occur at translation time. These types of errors are usually limited to files that contain embedded scriptlets.
v