- This topic has 3 replies, 3 voices, and was last updated 19 years, 3 months ago by
.
-
Posts
-
This is just a “little” convenience feature – which would nevertheless be *very* convenient:
I really like the “hot deployment” for webapp projects. However, I still frequently have to restart the web application – while restarting the appserver usually is NOT necessary. Restarting the webapp instead of the server is obviously much faster.
I mainly use Tomcat and am not so familiar with others. In Tomcat, you can restart webapps from the manager application.
Now: Couldn’t you integrate a little “restart/reload/stop/… webapp” into one of the menus? I’m sure most appservers support this feature.Finch
P.S.: Yes, I know that I can add a bookmark. But I’d need several bookmarks for each webapp and would have to update them when I change the deployment path or server. MyEclipse knows everything that’s needed…
Finch,
When I am working with a JSF Project and have it deployed to tomcat 5.0.x using exploded deployment, I have had trouble with tomcat picking up my new jsp pages. MyEclipse is correctly copying the new versions out to the deployment area on every save, but tomcat just doesn’t know to recompile the jsp.
One trick to get around this is to “touch” your web.xml file. Don’t make any real changes, but just by changing the modification date on the file, tomcat will reload the webapp context. This in effect will restart your web application.
Yes, JSP pages and so on are fine. Well, it’s actually “great” :-)))
(my favorite ME-feature 🙂This is about changes that require a restart of the webapp – e.g. changes to struts or hibernate config files (or changes to my own config files – not all settings are “reloadable”) or resource files which seem to be cached sometimes (at least the availability of certain languages)…
Yes, “touching” the web.xml is a workaround, but a constantly changing timestamp is not nice for version control.
Also, I’d have to open web.xml every time (or keep it open and look for it in the list of open files) which is not much better than setting a bookmark in the browser – after all, the manager application does provide this funtionality – this is just about convenience! I just don’t want to make 5 or more clicks to restart the webapp. Some days, I don’t have to restart the webapp at all, sometimes, I have to do it every couple of minutes, especially for troubleshooting…The priority for this is not THAT high, but sometimes it’s the small stuff that brings the “total experience” just a bit closer to being perfect 🙂
Wouldn’t the only requirement to reload a web-app be to touch the deployed version of web.xml? As far as I can see there shouldn’t be a need to touch the one in your workspace, should there?
It’s likely quite easy to write a simple Eclipse plug-in yourself that just does a touch web.xml. Using reflection you might hack the info concerning the deployment location out of the myeclipse plug-ins. (alhtough it’s probably easier to just give your own plug-in a little preference field for this 😉 )
