Re: Modify web.xml in production war file

2019-07-16 Thread Martynas Jusevičius
André, installers are platform-specific, Docker images are not. You do the changes within the image which is Linux-based, and then deploy the image on any host platform that supports Docker. Moreover you’re able to deploy different versions of Tomcat (or other image) on the same system. Most imag

Re: Modify web.xml in production war file

2019-07-16 Thread Mark Eggers
André: See comments inline. On 7/16/2019 4:37 PM, André Warnier (tomcat) wrote: > On 16.07.2019 19:54, Martynas Jusevičius wrote: >> Grigor, >> >> I think this is a use case that Docker containers at least partially >> address. >> >> I find deploying containers way easier to share/deploy and more

Re: Modify web.xml in production war file

2019-07-16 Thread tomcat
On 16.07.2019 19:54, Martynas Jusevičius wrote: Grigor, I think this is a use case that Docker containers at least partially address. I find deploying containers way easier to share/deploy and more platform-independent than WAR files. I’ve created a Tomcat-based image that accepts ENV variable

Re: Modify web.xml in production war file

2019-07-16 Thread Martynas Jusevičius
Grigor, I think this is a use case that Docker containers at least partially address. I find deploying containers way easier to share/deploy and more platform-independent than WAR files. I’ve created a Tomcat-based image that accepts ENV variables and modifies server.xml using their values: http

Re: Modify web.xml in production war file

2019-07-16 Thread Mark Thomas
On July 12, 2019 6:43:49 PM UTC, Grigor Aleksanyan wrote: >Hi Everyone, > >We have been shipping web application with war packaging in our >production >builds which contains a web.xml with few security sections. >This web.xml defines security constraints that are in most cases not >what >the fina

Modify web.xml in production war file

2019-07-12 Thread Grigor Aleksanyan
Hi Everyone, We have been shipping web application with war packaging in our production builds which contains a web.xml with few security sections. This web.xml defines security constraints that are in most cases not what the final deployment uses. This means that to update the war we need to save