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 41050 - File name change upper case to lower case is not recognized
Summary: File name change upper case to lower case is not recognized
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Pavel Buzek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-16 22:23 UTC by Ana.von Klopp
Modified: 2004-08-13 12:11 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ana.von Klopp 2004-03-16 22:23:51 UTC 
Create a web module and add a file called index.
jsp. Execute the web module. 

Change the name to Index.jsp. Try to execute it. 
It fails no matter what you do: reexecute, 
start/stop the server; start/stop the IDE. 

java.lang.NoClassDefFoundError: 
org/apache/jsp/Index_jsp (wrong name: 
org/apache/jsp/index_jsp)

I tried to delete the offending files by un-hiding 
the relevant work directory but that doesn't work 
either. I had to delete the work directory outside 
of the IDE and restart again.
Comment 1 Marek Fukala 2004-03-17 08:02:15 UTC 
Anna, are you sure this is a tomcatint module bug? The stacktrace from
catalina output states that the problem is in MonitorFilter. So maybe
the monitor module would be more appropriate.
Comment 2 Marek Fukala 2004-03-19 07:39:12 UTC 
Libore, could you please look at this?
Comment 3 L Martinek 2004-03-19 09:49:25 UTC 
This is not a issue of monitor, but also it's not a issue of
tomcatint. If you rename index.jsp to Index.jsp in a standalone
tomcat, the same exception is thrown. Could somebody fill a issue
against tomcat? I haven't account for tomcat's bugzilla.
Comment 4 Ana.von Klopp 2004-03-22 16:29:36 UTC 
Libor is correct in that the problem is in Tomcat itself, but since it 
affects IDE users we need to track it here and indicate that it 
depends on a bug in Tomcat. It seems like the web apps team probably 
needs to have some procedure for filing and tracking bugs in Tomcat. 

Marek, please note that the Monitor Filter (like the internal Tomcat 
classes) is invoked whenever Tomcat process a request. It is designed 
to rethrow any exception that it encounters in the process. That means 
that it always shows up in the stack trace, but it's only the culprit 
if the stacktrace ends with monitor code, so to speak. I know that's 
confusing...
Comment 5 Pavel Buzek 2004-08-06 20:11:42 UTC 
Cannot reproduce it. When testing with 5.0.24 I see this problem, but
in 5.0.27 it works.
Probably fixed in tomcat.

Anyway, just trying Redeploy helps even for 5.0.24 case. 
This bug has nothing to do with IDE.