pid-2 is right in that the path shouldn't be used here, if i remove this
Tomcat still deploys myapp.war as "/" as it's using the name of the ROOT.xml
file to infer the actual path.
i misread the tomcat context documentation
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html.
deploying y
Andrew Eells wrote:
> If it helps it's also possible to deploy your war file with any name at all
> and have it deployed as the default context "/" - without the need to name
> it ROOT.war.
>
> The trick is to have it located outside the Tomcat directory and have the
> ROOT.xml context docBase po
If it helps it's also possible to deploy your war file with any name at all
and have it deployed as the default context "/" - without the need to name
it ROOT.war.
The trick is to have it located outside the Tomcat directory and have the
ROOT.xml context docBase point to it whilst setting path="
..@gmail.com]
> > Subject: root context path - war file not unwar'd
> >
> > I have an issue where inside a i set the context path
> > of "/" to a directory inside webapps (myapp).
>
> This is bad practice, and gets your webapp deployed twice. Sound
> From: AD [mailto:straightfl...@gmail.com]
> Subject: root context path - war file not unwar'd
>
> I have an issue where inside a i set the context path
> of "/" to a directory inside webapps (myapp).
This is bad practice, and gets your webapp deployed twice.
Hello,
I have an issue where inside a i set the context path of "/" to a
directory inside webapps (myapp). The issue is when i delete the directory
, on first startup the directory is not available yet (not unwar'd yet it
appears) so it auto-sets the root context path to the default tomcat
appl
