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.
This is the same problem as documented in issue #60236, only this is happening with NB 5.0 beta. I have seen this happen on both my Linux (SuSE 9.2 Pro) and Windows XP systems. Unlike when I saw this problem in NB 4.1, in 5.0 this file is also corrupted when I build the project - the sun-web.xml that is included in my WAR file is *always* corrupt and the app cannot be deployed on my Sun App Server 7 without unpacking the WAR file and manually replacing the erroneous file.
Reporter, I think that this issue is duplicate of the issue #60236. Please, don't file two issues for same error. The issue shall be marked as duplicate. Thanks Petr
Petr - well, true, but since I closed bug #60236 as WONTFIX precisely because it was not 5.0, in this case I think a new bug is appropriate. Korb - I checked and the versioning code I referred to in my comment in 60236 didn't make it into 5.0 Beta, so you'll see the same problem there. This was fixed just after the beta went out so if you grab the latest Q build you should find that it works the way I explained. Closing as FIXED.
Verified
I have not downloaded the latest nightly build to test your fix, but I found another issue as a result of this one. In an attempt to keep the sun-web.xml file from being corrupted, I chmoded the file to be read-only (440). However, I now frequently see an error pop-up containing the following text: Cannot save configuration data for !PW FIXME server display name to !PW FIXME file list??? This is on SuSE Linux 9.2 Pro.
1) Please don't reopen an old bug to report a new different bug. 2) Regarding bogus content in message (e.g. FIXME) - this is fixed, can't remember the bug id. 3) Regarding "issues" when dealing with attemped saves to read-only files - this is reported and scheduled to be be fixed for 5.0. I can't seem to find the bug, but this aspect of the code will be scrubbed and all issues I can find about it fixed. Closing this issue again. If you want a tracking number for the read-only case, feel free to file a new bug and I'll comment there when this issue is taken care of (or mark it as a dupe of whatever the existing bug is, if I find it.)