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 spans some plugins (GF and TC for sure) and j2eeserver. here is a sequence that seems bad... register tomcat or GF create a web app that targets tomcat or GF run the web app (use run off the right-click menu for the project) the browser opens and displays the index.jsp switch to the Services explorer drill down to that app that was just run. select Stop from its right-click menu switch back to the project explorer Use Run again the browser opens and shows a 503 Add a servlet to the web app Use Run again the browser opens on index.jsp I expect the result of run 2 and run 3 to be consistent. I think the IDE should force the web app to be started/executable/whatever when the user uses the Run item on a project (or the Run Main Project).
side note: with DOS enabled... the app switches from stopped to runnable in situations where the user's last direct action related to the project's "runnability" was to direct the IDE to make the app stopped. So... new web app 4 tomcat Run the app the index.jsp appears in the browser set the app to stopped state Reload the app in the browser the app shows up as 503. add a servlet to the app (while the app is DOS) Reload the app in the browser The index.jsp shows up... but the last action on the project as to do a save... in this situation I would expect to see the 503 still...
As this hasn't been ever reported by the real (outside world) user and there are some complications (see below), I don't think we should take care of this in 6.5. The trouble is with server plugins implementation. While some of them implement start, others don't. Some plugins even do not provide stop action etc. The reason why plugins are so different is poor jsr-88 design and its implementation (server vendors). We can take look into thi after 6.5.