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.
1.5.0_07; Java HotSpot(TM) Client VM 1.5.0_07-b02 Windows XP version 5.1 running on x86 en_US (nb); Cp1252 Steps to reproduce: 1.Create new NetBeans Plug-in Modules|Module Project 2.Create new JFrame Form with name e.g. MyFrame 3.Create new Action and write to its performAction()method: new MyFrame().setVisible(true); When the action is invoked then the MyFrame form is not displayed. The problem is in code setDefaultCloseOperation(javax.swing.WindowConstants.EXIT_ON_CLOSE).
see 70145, i've also met this..
I'd argue that core/execution behaves right here. The SecMan just report that exit () is not allowed (and potentially kill the thread group trying to perform exit). It is strange that the JFrame mode setter checks the exit right that early, but the exception would be there after closing the window anyway (but swallowed one). It is questionable whether we should hide the ExitSecurityException in the AWT thread handler (as we're doing now) when the IDE no longer support internal execution. Not hiding it would immediatelly reveal the real problem (=you must not call System.exit() inside the IDE). Reassigning to core/code for evaluation (NbErrorManager does the filtering, cc-ing Yarda)
I do not think there is anything else to do. We need to prevent System.exit(0) and we do it using our own security manager. However, the jFrame.setDCO(EXIT_ON_CLOSE) uses the same query and there does not seem to be a way to distinguish between those two calls. Anyway even this one succeded, there would be the exception during closing the frame...
Marking issue as VERIFIED.