How to update a web app without uploading the WAR
Hello, My WAR file is becoming every time bigger and bigger, images are included and also some documents like PDFs Sometimes we need to change little code in only one jsp file, perhaps someone can help figuring out alternatives to upload and update specific changes to code regarding one single file ? I am using Tomcat 7.0.50, with Apache, using mod_jk working fine and usually deploying the web app with the tomcat manager on a Centos release 6.5 WAR is allready over 120M size. Thanks, Wilhelm. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to update a web app without uploading the WAR
You can update the single .jsp on the server, in at least some situations. I do that occasionally when I need to get an update out and can't take the service down. On 1/21/2014 12:02 PM, Chris Patterson wrote: Hello, My WAR file is becoming every time bigger and bigger, images are included and also some documents like PDFs Sometimes we need to change little code in only one jsp file, perhaps someone can help figuring out alternatives to upload and update specific changes to code regarding one single file ? I am using Tomcat 7.0.50, with Apache, using mod_jk working fine and usually deploying the web app with the tomcat manager on a Centos release 6.5 WAR is allready over 120M size. Thanks, Wilhelm. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to update a web app without uploading the WAR
On 1/21/14 9:59 AM, David kerber wrote: You can update the single .jsp on the server, in at least some situations. I do that occasionally when I need to get an update out and can't take the service down. But note that if and when you DO replace the WAR file, it will stomp on whatever changes you've made in the context. -- JHHL (speaking from bitter experience) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to update a web app without uploading the WAR
On 1/21/2014 1:55 PM, James H. H. Lampert wrote: On 1/21/14 9:59 AM, David kerber wrote: You can update the single .jsp on the server, in at least some situations. I do that occasionally when I need to get an update out and can't take the service down. But note that if and when you DO replace the WAR file, it will stomp on whatever changes you've made in the context. Yes, but in my use case that's ok. I replace the .jsp first, and then when I can stop the service I replace the entire .war file, which will include the new .jsp. -- JHHL (speaking from bitter experience) Yup, me too, when I once forgot to push the updated .jsp into the new .war file. Never happened again, though. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to update a web app without uploading the WAR
On Jan 21, 2014, at 1:55 PM, James H. H. Lampert jam...@touchtonecorp.com wrote: On 1/21/14 9:59 AM, David kerber wrote: You can update the single .jsp on the server, in at least some situations. I do that occasionally when I need to get an update out and can't take the service down. But note that if and when you DO replace the WAR file, it will stomp on whatever changes you've made in the context. You can get around this if you deploy from an exploded WAR directory instead of a WAR file. As an example, the manager application does this. Dan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to update a web app without uploading the WAR
Thanks for your suggestions, I will try this last one. Indeed, not all replacements had a good experience with some specific files. Do you know if there is some plugin for Eclipse that helps to do updates or sync just for the last changes done, or only just for one single file to be replaced, together with its associated files for successfull micro updates ? Dreamweaver has a facility to upload a single file for replacement and asks if associated files should also be uploaded. Remote connection is previosly configured and tested. I just couldn't find something similar. Chris El 21/01/2014 02:03 p.m., Daniel Mikusa escribió: On Jan 21, 2014, at 1:55 PM, James H. H. Lampert jam...@touchtonecorp.com wrote: On 1/21/14 9:59 AM, David kerber wrote: You can update the single .jsp on the server, in at least some situations. I do that occasionally when I need to get an update out and can't take the service down. But note that if and when you DO replace the WAR file, it will stomp on whatever changes you've made in the context. You can get around this if you deploy from an exploded WAR directory instead of a WAR file. As an example, the manager application does this. Dan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to update a web app without uploading the WAR
On Tue, Jan 21, 2014 at 11:14 AM, Chris Patterson tom...@vittox.com wrote: Indeed, not all replacements had a good experience with some specific files. Do you know if there is some plugin for Eclipse that helps to do updates or sync just for the last changes done, or only just for one single file to be replaced, together with its associated files for successfull micro updates ? I would seriously reconsider a deployment strategy that packs lots of large static resources (images, PDFs) along with code. Being able to just do a standard deploy regardless of the scope of changes makes for a lot less mental overhead :-) FWIW, -- Hassan Schroeder hassan.schroe...@gmail.com http://about.me/hassanschroeder twitter: @hassan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
