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.
Summary: | JSP execution in Webmodules often doesn't work. | ||
---|---|---|---|
Product: | javaee | Reporter: | Marek Fukala <mfukala> |
Component: | Code | Assignee: | Petr Jiricka <pjiricka> |
Status: | CLOSED FIXED | ||
Severity: | blocker | ||
Priority: | P1 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | The page displayed in browser (also contains the exception). |
Description
Marek Fukala
2001-04-10 14:29:22 UTC
Created attachment 1067 [details]
The page displayed in browser (also contains the exception).
The compilation "seems to work". If you only compile a JSP page neither error nor exception is displaed, but when you try to execute the JSP file, web browser shows the exception from attachement. In the first paragraph there should be of course "when you try to execute ..." bug doesn't appear any more Oops, this bug appeared to me again. The exception in browser says that the class _0002faaa_0002ejspaaa_jsp_0 can't be loaded. And actually I didn't find this class. Directory <forte_user>\jspwork\Tomcat+3.2\207d9f5d contain these files: _0002faaa_0002ejspaaa_jsp_0.java _0002faaa_0002ejspaaa_jsp_1.java _0002faaa_0002ejspaaa_jsp_2.java _0002faaa_0002ejspaaa.class The fact that file _0002faaa_0002ejspaaa_jsp_0.class does not exist is not significant, because Tomcat's classloader uses a file name which is different from the actual class name. I have't been able to reproduce this, so marking as "worksforme". Still appears. IN=1869, fixed on May 11, 2001 by making sure that the Tomcat config file is written out by the IDE before Tomcat reads it. Still apears in continuous build 20010511-1625. Fixed on 15-May-2001 verified in 010515 Resolved for 3.4.x or earlier, no new info since then -> closing. |