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.
It's frequent when developing a tomcat application to stop and restart tomcat server for testing against last code update. Netbeans stops tomcat server successfully, but when you want to run your tomcat application, you will see this steps: 1.- application compiles 2.- tomcat startup 2.1.- Tomcat starts previous version of app 2.2.- netbeans undeploys previous app 2.3.- netbeans deploys the new version of app 3.- everything it's ok and beautiful! If this application takes some time to initialize (about 30 seconds due to several database preloads and checks... inherent to the app). In a restart developer has to wait 30 seconds for previous app version starting (+ undeploy), plus 30 seconds for the new version. Is possible to develop a new button called: "Undeploy and stop" (such as clean and build), this button firstly undeploys netbeans-deployed applications and then stops tomcat. When tomcat is restarted, it will do its startup and then the application deployer will deploy directly the new version of the app. sorry for my terrible english!
I find this behaviour quite annoying. Not only does it double the time for a change to be reflected, but I have to take care when studying the log that I'm not in fact looking at the previous version. Since I'm letting Netbeans manage tomcat for me I don't see why it can't undeploy the app I'm deploying first if it exists before starting tomcat.