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: | EXECUTION: valid web module cannot be run | ||
---|---|---|---|
Product: | javaee | Reporter: | Ana.von Klopp <avk> |
Component: | Code | Assignee: | Petr Jiricka <pjiricka> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows ME/2000 | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
WAR of web app that reproduces the problem
WAR of web app that reproduces the problem |
Description
Ana.von Klopp
2002-07-23 02:30:48 UTC
Created attachment 6850 [details]
WAR of web app that reproduces the problem
Created attachment 6851 [details]
WAR of web app that reproduces the problem
Configuration: JDK1.4, Netbeans 3.4 daily builds from Monday 7/22 and 7/19. FWIW, WAR sample has a built in bug to demo monitor functionality. *** This issue has been marked as a duplicate of 23135 *** This is not a dupe - they're related, but it's not a dupe. The other bug says that you cannot run compile all on a web module. That I can live with, because I can execute the web module and the server will compile the files as necessary. This bug reflects a change in the IDE's behaviour, which is that when I deploy a web module which has more than one file of the same name (I did not run the compile all action), the IDE automatically attempts to run the compile all action which means that I can no longer execute the module at all. This is worse than the other problem, and represents a regression from the user's point of view. The fix should be not to compile the whole WM when executing/deploying it, then. That would fix the problem until the other bug is fixed, yes, so I think this is good in the interim. Fixed as suggested: When WEB-INF is compiled, only compile the 'classes' subdirectory, not the objects contained in WEB-INF. Verified in S1S build 030217_1 *** Issue 33911 has been marked as a duplicate of this issue. *** |