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 starting up tomcat, either through F6 or manually it does not list up in the Execution view. This was a very useful feature in nb3.5 as it reduces the 'jumping around to shut it down'. I hope this is only a broken feature and not a new one.
Since the way how webmodules are deployed to j2ee servers has changed dramitically, this -feature- has been removed. Now you can add an already running external tomcat server without need to run it from the IDE. So at least in that case having a process displayed in the runtime tab would have no sense. You can simply start/stop server throught server registry node - it contains nodes representing all you registered servers. From nb3.6 it is not necessary to shutdown server to take your changes in webmodule into account since it uses tomcat manager application to sttart/stop/reload/deploy/undeploy them automatically. If you still consider this in spite of what I have written, please let me know, otherwise I will close this as 'AS DESIGN' bug. Thaks, Marek
marking as enhancement
After playing aroung a bit I found the new context/server handling quite neat. Although it's still more complicated to stop/undeploy a context/server (start through F6 stayed the same). Before (nb3.5) I just killed the task in execution view. Now I need to change tab and find the node (even need to refresh 'Web Modules' if i changed the context) for that. To retain at least the same useability it would be necessary to add a start/stop/redeploy (or similar) into the context menu of the WEB-INF node - I know the context menu there is already quite large...
Hi Thomas, The webmodule should detect changes in deployment descriptor / classes and automatically reload the webmodule when you execute it. If this do not happen, it's a bug. Could you please describe your case when you really need to do the reload/undeploy manually? Thaks Marek
As it is in our application we have quite a lot of configuration files outside of the deployment descriptor, so if i change something there this will naturally not be detected. Of course you would say then, that it would be appropriate to write some functionality ourselfes to watch for changes in the config files. Well until now we didn't need to do that, because starting/stopping the context of the server was sufficient and in production phase this is a rare case anyway. It was only necessary to manually start/stop when we changed behaviour in those files or if an error occured during startup (and the application didn't stop again).
Some time ago there was a suggestion to have an additional action like 'Execute & reload' available on webmodule node, which would do the some as Execute + reloading (start/stop) of the webmodule. This could be used when an user does a change in a file which is not checked for newer version (like you mentioned the properietary configuration files) or when s/he simply wants to reset the state of the application. Would it be sufficient for you? If so please let me know and I would use you vote as an argument for people who are making the design of future versions of netbeans.
Sounds to be a good idea and reasonable enhancement to the current implementation.
It has been fixed in 4.0 1) There's 'Redeploy Project' action in project's context menu 2) WEB-INF/**.xml and WEB-INF/**.dtd trigger web application reload I hope you will find this solution sufficient.
This sounds like exactly the thing i was looking for... Curiouse how it will work in action.. thanx :)