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.

Bug 30715 - TCAT: Compilation error when JSP in subdirectory uses bean in WEB-INF/classes
Summary: TCAT: Compilation error when JSP in subdirectory uses bean in WEB-INF/classes
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: All All
: P4 blocker (vote)
Assignee: Petr Jiricka
URL: http://nagoya.apache.org/bugzilla/sho...
Keywords: TOMCAT
: 25573 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-02-06 02:17 UTC by Jason Rush
Modified: 2008-12-24 04:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Rush 2003-02-06 02:17:50 UTC
Description: 
Build 010619:
When a JSP is in a subdirectory of a web module and includes a bean which is in
the web module's WEB-INF/classes directory, the following compiler error is
encountered.  If the JSP is in the root directory of the web module, it will
compile without error.

test/_0002ftest_0002ftest_0002ejsptest_jsp_0.java [67:1] cannot resolve symbol
symbol  : class Foo
location: class test._0002ftest_0002ftest_0002ejsptest_jsp_0
                    Foo test = new Foo();
                    ^
                    
test/_0002ftest_0002ftest_0002ejsptest_jsp_0.java [67:1] cannot resolve symbol
symbol  : class Foo
location: class test._0002ftest_0002ftest_0002ejsptest_jsp_0
                    Foo test = new Foo();
                                   ^
                                   
2 errors
Errors compiling test.


Public Summary: 
When a JSP is in a subdirectory of a web module and includes a bean which is in
the web module's WEB-INF/classes directory (no package), the JSP will not
compile. The same error, though with a more informative message, occurs in 
Tomcat. 

This problem will not be fixed for FFJ3.0, but we will make sure that the 
documentation explains it, and if possible provide a more informative error
message. 

Evaluation: 
This is a well known problem in Tomcat, although right now I can't find the
number of the Tomcat bug.

Tomcat needs to change the way import statements are generated in the generated
servlet.
 
Need to fix in Tomcat. 
pjiricka@netbeans.org 2002-04-29

A comment.
Comment 1 Jason Rush 2003-02-06 02:19:04 UTC
Transferred from BugTraq 4472588.
Comment 2 Petr Jiricka 2003-03-03 10:44:59 UTC
Since JDK 1.4, importing classes from the default package 
is illegal. So this is not really a bug, however there 
should be a more user-friendly error message. This 
requires a fix in Tomcat. 

Need to check the behavior in Tomcat 5, and potentially 
file a Tomcat enhancement. Setting target milestone to NB 
4.0.
Comment 3 Petr Jiricka 2004-07-26 19:48:39 UTC
Tomcat 5.0.27 still displays the same compilation error message, now
for both JSPs in docRoot and in a subdirectory. The message still
could be more informative. 

However, now the situation is better because we display a warning when
the user creates a Java class in the default package.
Comment 4 Petr Jiricka 2004-09-15 22:58:17 UTC
The Tomcat issue is
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10714
Comment 5 Petr Jiricka 2004-09-15 23:00:07 UTC
*** Issue 25573 has been marked as a duplicate of this issue. ***
Comment 6 Jayashri Visvanathan 2008-12-24 04:10:38 UTC
Very old bug based on 3.3. Please reopen if this is still an issue in 6.5