> And that is for development, for deployment I have a bigger problem because > it is under Tomcat 6 which is behind AJP fronted by MS IIS. > And if the application is packaged from maven as a WAR, then all the classes > are inside packed in a JAR, which Tomcat extracts in a temporary place and > sometimes is not refreshed even if you bring a newer WAR. > So I have to stop the application, clean the WAR, clean the extracted > folders, clean the temp and work folders ... > >
^^^^^ I have exactly this scenario and it's a PITFA. Another option is to use eclipse's "Export to War" feature if you are using WTP. It doesn't bundle your classes into a jar first. There's probably also a maven option to leave your classes un-jarred, if that saves you time. (I don't know for sure) In any case, class reloading and war redeploys have always been harder than they should be, especially if you're trying to get the tomcat manager to stop the web app and redeploy. I have a batch file to delete the old war and exploded war and copy over the new one. Then I start up the service again and it explodes my war. Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
