Re: Strange behavior when deploying new war

2020-04-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 John, On 4/23/20 15:19, John Larsen wrote: > Ah doing ROOT.war is my pet peeve. I find this bad practice. Its > nice to have ROOT especially when the developer insists theres > something wrong with tomcat when really its their webapp. Having > ROOT

Re: Strange behavior when deploying new war

2020-04-23 Thread John Larsen
Turns out the developer was deleting the app dir along with war and restarting. John On Thu, Apr 23, 2020 at 1:19 PM John Larsen wrote: > Ah doing ROOT.war is my pet peeve. I find this bad practice. Its nice to > have ROOT especially when the developer insists theres something wrong with > tomc

Re: Strange behavior when deploying new war

2020-04-23 Thread John Larsen
Ah doing ROOT.war is my pet peeve. I find this bad practice. Its nice to have ROOT especially when the developer insists theres something wrong with tomcat when really its their webapp. Having ROOT intact, can show that by removing their webapp and tomcat works. As for "/" vs "" - not sure that wo

Re: Strange behavior when deploying new war

2020-04-23 Thread Mark Thomas
On 23/04/2020 20:10, John Larsen wrote: > Ok so my next question is how to handle this better? The goal here is so > that one does not have to enter /webappName/ on the end of the domain. > We use the context to tell Tomcat which webapp to load instead of ROOT. Name the file "ROOT.war" And if you

Re: Strange behavior when deploying new war

2020-04-23 Thread John Larsen
Ok so my next question is how to handle this better? The goal here is so that one does not have to enter /webappName/ on the end of the domain. We use the context to tell Tomcat which webapp to load instead of ROOT. John Larsen On Thu, Apr 23, 2020 at 12:47 PM Christopher Schultz < ch...@christo

Re: Strange behavior when deploying new war

2020-04-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 John, On 4/23/20 14:38, John Larsen wrote: > New tomcats 9.0.34 seems to fail when uploading new war when theres > a context in server.xml pointing to the particular exploded war. > Says 'The main resource set specified is not valid.' It's like hot

Strange behavior when deploying new war

2020-04-23 Thread John Larsen
New tomcats 9.0.34 seems to fail when uploading new war when theres a context in server.xml pointing to the particular exploded war. Says 'The main resource set specified is not valid.' It's like hot deploy is deleting the old webapp and restarting tomcat? To work around this one has to comme