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.
When I debug a java ee application, I usually step through some lines of code, locate an issue, fix the code and then choose to redeploy. The build process starts normally but fails *at the very end*, since the server is in "suspended" state. It would be much more convenient if the debugging session was automatically stopped when I choose Deploy/Run/Debug. Calling a Deploy/Run/Debug action is a conscious activity, and thus stopping the current debugging session seems to be quite safe from the usability standpoint. -- I'm working with NetBeans IDE Dev (Build 200610231500) 1.6.0-rc; Java HotSpot(TM) Client VM 1.6.0-rc-b104 Windows XP version 5.1 running on x86 ru_RU (nb); Cp1251
Should be reviewed by the usability team, IMO.
Petr, what do you think about it?
To be sure. The server is stopped in a breakpoint and the breakpoint is still active. If you try to run or debug the application again in this situation the build fails and you get a message: "Cannot perform required operation, since the server is currently in suspended state and thus cannot handle any requests." If user wants to redeploy, run or debug again he has to finish debug session and then invoke Debug/Run/Undeploy and Deploy action. He also can invoke Continue action and then invoke Debug/Run/Undeploy and Deploy action, but there is a risk, that the server will stop on another breakpoint and will be suspended. So for me it seams to be reasonable that "Debug" and "Undeploy and Deploy" actions should stop debug session, redeploy the application and start the debug session again. The "Run" action should stop debug session and redeploy the application.
this seems very similar/related to issue 86990... I a going to mark it as a dup. *** This issue has been marked as a duplicate of 86990 ***