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.
Create a web/ejb/ear module with server = sun appserver. Set the readonly attribute of the sun specific configuration file (e.g. sun-web.xml). Open the gui config editor on this file, make a change and save the file. There should be an Access Denied error when trying to write the file. It will be displayed twice, once by us, and once by the caller of our SaveCookie's save() method, since we must throw IOException to that caller to notify them of the failure. We display the error nicely because certain callers do not (see issue 69678). There will be duplicate dialogs shown for the follow methods of forcing a save. 1) Save All action (menu or toolbar button - key shortcut too if there is one.) 2) Save action (via ^S or menu) 3) IDE Exit followed by <Save> or <Save All> action in Exit Dialog. There will not be a duplicate dialog in the case where the user clicks the [X] to close the editor when there are unsaved changes. In this case, the caller mentioned above is us and our code does not show the duplicate message because it knows a message has already been displayed.
Can't fix the duplicate message until ExitDialog is cleaned up.
what is the story on this one? Raising to get this back on the radar..
The story is that issue 69678 (note dependency) isn't fixed yet so presumably we can't do anything about this issue. I suppose the new multiview editor might not have this problem but I doubt it as 69678 was not editor specific. Not worth the time to investigate to be certain, IMO. At least not right now.
Setting to future. Status of 69678 is unchanged.
Please be ready to discuss this issue on 2008/10/22
What's to discuss? Until 69678 is resolved, save() must throw an IOException, resulting in the not so nice message (hence the duplication). Not much we can do except wait.
let's work through that on 2008/10/22
P4 since we can't do anything until 69678 is fixed.
not worth worrying about in 7.0 time frame