Ok, it works that way. So, if I did want to create the WAR file, is my
structure correct to work with a virtual host?
Caldarale, Charles R wrote:
>
>> From: tomcatastrophe [mailto:nab...@changethings.org]
>> Subject: RE: Tomcat WAR deployment with virtual host only shows blank
&g
> From: tomcatastrophe [mailto:nab...@changethings.org]
> Subject: RE: Tomcat WAR deployment with virtual host only shows blank
> page
>
> So, I should package my WAR then?
Not necessarily; you can deploy it expanded, but with the directory name ROOT,
not ROOT.war.
Thanks Chuck. So, I should package my WAR then?
Caldarale, Charles R wrote:
>
>> From: tomcatastrophe [mailto:nab...@changethings.org]
>> Subject: RE: Tomcat WAR deployment with virtual host only shows blank
>> page
>>
>> Yes, it is a directory. What is odd
> From: tomcatastrophe [mailto:nab...@changethings.org]
> Subject: RE: Tomcat WAR deployment with virtual host only shows blank
> page
>
> Yes, it is a directory. What is odd is that it copies the
> META-INF/context.xml to the /tomcat/conf/Catalina/foo.com folder...
Not somet
:
>
>> From: tomcatastrophe [mailto:nab...@changethings.org]
>> Subject: Tomcat WAR deployment with virtual host only shows blank page
>>
>> If I rename the ROOT.war to ROOT it starts up fine. Does it matter if
>> the .war file is packed or unpacked and just named .WAR?
> From: tomcatastrophe [mailto:nab...@changethings.org]
> Subject: Tomcat WAR deployment with virtual host only shows blank page
>
> If I rename the ROOT.war to ROOT it starts up fine. Does it matter if
> the .war file is packed or unpacked and just named .WAR?
Are you saying t
looks in META-INF and finds and copies the context.xml to the
conf/Catalina/foo.com folder, but it still just serves a white page.
Thanks!!!
--
View this message in context:
http://www.nabble.com/Tomcat-WAR-deployment-with-virtual-host-only-shows-blank-page-tp24197704p24197704.html
Sent from the
