James,
On 9/25/23 12:17, James H. H. Lampert wrote:
I probably asked the question before, but does Tomcat have any problems
with not having a ROOT context?
I always run with a ROOT context just to be able to do things like
provide custom responses with clients request
/no-such-app
On 25/09/2023 17:17, James H. H. Lampert wrote:
I probably asked the question before, but does Tomcat have any problems
with not having a ROOT context?
None I am aware of although there may be some edge cases. Past
precedence is that any such edge cases would be treated as bugs and
fixed in
On Mon, Sep 25, 2023 at 12:20 PM James H. H. Lampert
wrote:
>
> I probably asked the question before, but does Tomcat have any problems
> with not having a ROOT context?
Not that I can tell and have been running in this mode for about 5 years now.
--
Aryeh M. Friedman, Lead Develo
I probably asked the question before, but does Tomcat have any problems
with not having a ROOT context?
--
James H. H. Lampert
Touchtone Corporation
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional
Jerry,
On 7/9/21 01:58, Jerry Malcolm wrote:
I have one webapp that processes REST-style url paths and therefore
needs to run in the ROOT context.
I'm not sure the conclusion follows from the premise, here. You can
certainly use REST-style URL paths and not have a context at the top-
On 7/9/2021 2:23 AM, Olaf Kock wrote:
On 09.07.21 07:58, Jerry Malcolm wrote:
I have one webapp that processes REST-style url paths and therefore
needs to run in the ROOT context. Is it possible to run other webapps
in the same host with other non-root contexts? In other words, when
On 09/07/2021 08:23, Olaf Kock wrote:
On 09.07.21 07:58, Jerry Malcolm wrote:
I have one webapp that processes REST-style url paths and therefore
needs to run in the ROOT context. Is it possible to run other webapps
in the same host with other non-root contexts? In other words, when
On 09.07.21 07:58, Jerry Malcolm wrote:
> I have one webapp that processes REST-style url paths and therefore
> needs to run in the ROOT context. Is it possible to run other webapps
> in the same host with other non-root contexts? In other words, when
> resolving a URL to a web
I have one webapp that processes REST-style url paths and therefore
needs to run in the ROOT context. Is it possible to run other webapps
in the same host with other non-root contexts? In other words, when
resolving a URL to a web app, does it try to map the url to the defined
context
t; https://frobozz.example/aux. The load balancer then routes the requests
> to the proper sub-cluster.
>
> Because of the way things work with the load balancer, it expects to
> find the main entry point as the ROOT context of the main sub-cluster,
> and expects to find the oth
sub-cluster.
Because of the way things work with the load balancer, it expects to
find the main entry point as the ROOT context of the main sub-cluster,
and expects to find the other two as the "reports" context of the report
cluster, and the "aux" context of the auxiliary clu
On 15/05/2017 14:49, mwbxtr wrote:
I believe I am having an issue with getting the ROOT context from a different
app context. This was working in 8.0.14, but no longer works in 8.0.43.
This works for me with a clean build of 8.0.x.
You'll need to put together the simplest test case
I believe I am having an issue with getting the ROOT context from a different
app context. This was working in 8.0.14, but no longer works in 8.0.43.
Root context exists and (includes crossContext=true in conf/context.xml)
Within Context: /app1
public class CrossContextExample
>> I understand that application deploy order is the key to get context to
>>>> deployed applicaitons (when application isn't deployed i can't get it
>>>> context - it is clear).
>>>> But ROOT application is deployed before app1, but i c
o
>>> deployed applicaitons (when application isn't deployed i can't get it
>>> context - it is clear).
>>> But ROOT application is deployed before app1, but i can't get ROOT context
>>> from app1.
>>> Is it in tomcat 8 possible to get ROOT
x27;t get it
>> context - it is clear).
>> But ROOT application is deployed before app1, but i can't get ROOT context
>> from app1.
>> Is it in tomcat 8 possible to get ROOT context from other
>> application (in servlet) ? If yes, coud tou give me an simple examp
before app1, but i can't get ROOT context
> from app1.
> Is it in tomcat 8 possible to get ROOT context from other
> application (in servlet) ? If yes, coud tou give me an simple example ?
>
> In tomcat 6 when i put this configuration to server.xml
>
> />
>
> i hav
Thanks for answer.
I understand that application deploy order is the key to get context to
deployed applicaitons (when application isn't deployed i can't get it
context - it is clear).
But ROOT application is deployed before app1, but i can't get ROOT
context from app1. *Is
t /app1 : null
> Context /app2 : null
>
> Servlet START: /app2
> Context / : null
> Context /app1 : org.apache.catalina.core.ApplicationContextFacade@8c6fb37
> Context /app2 : null
>
>
> I debug source of tomcat and find, that ROOT context (with empty "path"
&g
t; />
And the output is:
Servlet START: /app1
Context / : null
Context /app1 : null
Context /app2 : null
Servlet START: /app2
Context / : null
Context /app1 : org.apache.catalina.core.ApplicationContextFacade@8c6fb37
Context /app2 : null
I debug source of tomcat and find, that ROOT context (wi
Hey there,
I'm trying to deploy a war of my application to the root context. I name it
ROOT.war and it autodeployed fine. When I try to add versioning like
ROOT##1.war and ROOT##2.war, it seems to see the context as ##1 and fail to
deploy. For example, I get exceptions saying it couldn&#
Hello to all,
I am using Tomcat 7.0.29 (from ZIP got at Tomcat Apache site), Oracle Linux 6.4
and want to deploy "myapp" to ROOT context using virtualhost. My actual
settings is according Tomcat documentation
http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Naming
If y
On 14/05/2014 09:04, Junek Leoš wrote:
> Hello to all,
>
> I am using Tomcat 7.0.29 (from ZIP got at Tomcat Apache site), Oracle Linux
> 6.4 and want to deploy "myapp" to ROOT context using virtualhost. My actual
> settings is according Tomcat documentation
>
>
6 AM
> To: Tomcat Users List
> Subject: Re: Root context switching
>
> Hello,
>
> If my idea was only as simple as renaming it to ROOT.war (this one I
> know
> of):)
> Basic what I want is the same functionality which google apps provides.
> So I want to be able to h
On 04.09.2012 13:26, Dennie.nl wrote:
Basic what I want is the same functionality which google apps
provides. So
I want to be able to have multiple versions of my application online,
let
people try the new environment and eventually switch the root context
to
the new running version. This
>
> Basic what I want is the same functionality which google apps provides. So
> I want to be able to have multiple versions of my application online, let
> people try the new environment and eventually switch the root context to
> the new running version. This enables my clients
:
> > hostname\myappv1
> > hostname\myappv2
> >
> > Now I want the ROOT context to be set dynamicly to one of the available
> > deployed versions. Is this possible? Is there a way to implement this?
> >
> > Dennie,
>
> This question is asked regularly. The
I am new to Tomcat. What I like to do is to deploy different versions of my
> application, for example:
> hostname\myappv1
> hostname\myappv2
>
> Now I want the ROOT context to be set dynamicly to one of the available
> deployed versions. Is this possible? Is there a way
l-script copies to any instance (1..n) a built
> .war-file whose filename-suffix varies on application, version, timestamp
> and build-id. The scripts copies the .war into the instance-i/webapps
> directory via cp over ssh in the intranet.
>
> My question is how to mount the .war-file
ipts copies the .war into the instance-i/webapps
directory via cp over ssh in the intranet.
My question is how to mount the .war-file 'dynamically' as the instance's
root context application?
Currently all .war builds have a fixed name, assume myapp-3.2.war, and all
server.xml&#
On 08/08/2011 10:30, jenskreidler wrote:
>
>
> Pid * wrote:
>>
>> On 08/08/2011 09:56, jenskreidler wrote:
>>>
>>> Hi tomcat-users,
>>>
>>> using tomcat 7, is it possible to mount the ROOT context path for a .war
>>> file, w
Pid * wrote:
>
> On 08/08/2011 09:56, jenskreidler wrote:
>>
>> Hi tomcat-users,
>>
>> using tomcat 7, is it possible to mount the ROOT context path for a .war
>> file, where the .war file will have a variable file name, i.e. building a
>> .war
On 08/08/2011 09:56, jenskreidler wrote:
>
> Hi tomcat-users,
>
> using tomcat 7, is it possible to mount the ROOT context path for a .war
> file, where the .war file will have a variable file name, i.e. building a
> .war by a continuous integration server.
> For example,
Hi tomcat-users,
using tomcat 7, is it possible to mount the ROOT context path for a .war
file, where the .war file will have a variable file name, i.e. building a
.war by a continuous integration server.
For example, you get a myapp-3.2.0-20110809-build254.war, next day a
myapp-3.2.0-20110810
> From: genera...@googlemail.com [mailto:genera...@googlemail.com] On
> Behalf Of James McArthur
> Subject: Re: Tomcat reload defaultt ( root ) context for web app in
> host
>
> Thanks for the help so where do I put my then - its
> working across all my servers like this ?
t;> Subject: Re: Tomcat reload defaultt ( root ) context for web app in
>> host
>>
>> > xmlValidation="false" xmlNamespaceAware="false">
>> 1.2.3.4
>>
>> > global="jdbc
> From: genera...@googlemail.com [mailto:genera...@googlemail.com] On
> Behalf Of James McArthur
> Subject: Re: Tomcat reload defaultt ( root ) context for web app in
> host
>
> xmlValidation="false" xmlNamespaceAware="
m]
> > Subject: Tomcat reload defaultt ( root ) context for web app in host
> >
> > If you try and start or stop the / context it says no such context
> > exist (although it really does).
>
> Works fine for me on 6.0.24 using Tomcat's manager webapp. Besides the
> From: James McArthur [mailto:genera...@googlemail.com]
> Subject: Tomcat reload defaultt ( root ) context for web app in host
>
> If you try and start or stop the / context it says no such context
> exist (although it really does).
Works fine for me on 6.0.24 using Tomcat&#
On 23/02/2010 10:19, James McArthur wrote:
Hi
I have been using Tomcat for years since 3 till 6 but I have never worked
this one out
I have several in my engine each with a manager
I have web apps intalled including a website in the ROOT context ( e.g. /
) for each host
If you try and
Hi
I have been using Tomcat for years since 3 till 6 but I have never worked
this one out
I have several in my engine each with a manager
I have web apps intalled including a website in the ROOT context ( e.g. /
) for each host
If you try and start or stop the / context it says no such
invalid path
path="/ "
try
path=""
On 08/28/2009 02:57 AM, Jan Jonas wrote:
I have a very annoying problem with tomcat 6:
ServletContext.getContext() always returns null if I call the method from the "root" context, i.e.
the context I have defined with pat
On 28/08/2009 09:57, Jan Jonas wrote:
I have a very annoying problem with tomcat 6:
ServletContext.getContext() always returns null if I call the method from the "root" context, i.e.
the context I have defined with path="/" in my server.xml. I also tried setting path=&
I have a very annoying problem with tomcat 6:
ServletContext.getContext() always returns null if I call the method from the
"root" context, i.e. the context I have defined with path="/" in my server.xml.
I also tried setting path="" (I read that this could fix pro
-
Von: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Gesendet: Mittwoch, 12. August 2009 16:10
An: Tomcat Users List
Betreff: RE: change the default JSP index.jsp for ROOT context in Tomcat 6
> From: Jörg Spilling [mailto:spill...@equicon.de]
> Subject: AW: change the defa
> From: Jörg Spilling [mailto:spill...@equicon.de]
> Subject: AW: change the default JSP index.jsp for ROOT context in
> Tomcat 6
>
> (and it's not odd: it's a "security" hint - simply hide it!)
If you think that constitutes security, you're fooling
...@unisys.com]
Gesendet: Mittwoch, 12. August 2009 15:51
An: Tomcat Users List
Betreff: RE: change the default JSP index.jsp for ROOT context in Tomcat 6
> From: Jörg Spilling [mailto:spill...@equicon.de]
> Subject: AW: change the default JSP index.jsp for ROOT context in
> Tomcat 6
>
> From: Jörg Spilling [mailto:spill...@equicon.de]
> Subject: AW: change the default JSP index.jsp for ROOT context in
> Tomcat 6
>
> I want no own ROOT application. I will disable the access to the
> manager application by using http://localhost:8080/. On Tomcat 5, I
> have
-Ursprüngliche Nachricht-
Von: Pid [mailto:p...@pidster.com]
Gesendet: Mittwoch, 12. August 2009 15:34
An: Tomcat Users List
Betreff: Re: change the default JSP index.jsp for ROOT context in Tomcat 6
On 12/08/2009 14:26, Jörg Spilling wrote:
> I'm running Tomcat 6 on Linux and I want
On 12/08/2009 14:26, Jörg Spilling wrote:
I'm running Tomcat 6 on Linux and I want change the index.jsp of the ROOT
context which is displayed by http://localhost:8080/.
For Tomcat 5 I could comment out the index_jsp mapping in web.xml for ROOT. The
web.xml for the ROOT in Tomcat 6 do
I'm running Tomcat 6 on Linux and I want change the index.jsp of the ROOT
context which is displayed by http://localhost:8080/.
For Tomcat 5 I could comment out the index_jsp mapping in web.xml for ROOT. The
web.xml for the ROOT in Tomcat 6 doesn't contain such a mapping. So how could
ent
>>
>
>
> -----
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
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
st setting path="". Exact details
can be found here:
http://www.andrew-eells.com/2009/03/21/tomcat-root-war/ Tomcat ROOT.war
deployment
--
View this message in context:
http://www.nabble.com/root-context-path---war-file-not-unwar%27d-tp21553536p22691178.html
Sent from the Tomcat - Use
..@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
[EMAIL PROTECTED] wrote:
hmm, I had those set = True for both, and I was getting that behavior,
only when I set them both to false does it not seem to create the temp
directories. maybe something else?
Sorry - just did a copy and paste from your config. Setting them true is
what causes the
hmm, I had those set = True for both, and I was getting that behavior,
only when I set them both to false does it not seem to create the temp
directories. maybe something else?
On Feb 27, 2008, at 2:31 PM, Mark Thomas wrote:
> AH NF wrote:
>> Hi all,
>> Ok so I have my ROOT.war and "/" host
Ok, so it seems that if I have both of those settings = "false", I
don't get the 0-ROOT stuff created in /temp, however on application
stop and undeploy I have lingering jars leftover and a new deploy will
not unpack because the ROOT dir already exists
On Feb 27, 2008, at 2:31 PM, Mark Thom
Ok, so it seems that if I have both of those settings = "false", I
don't get the 0-ROOT stuff created in /temp, however on application
stop and undeploy I have lingering jars leftover and a new deploy will
not unpack because the ROOT dir already exists
On Feb 27, 2008, at 2:31 PM, Mark Tho
hmm, I had those set = True for both, and I was getting that behavior,
only when I set them both to false does it not seem to create the temp
directories. maybe something else?
On Feb 27, 2008, at 2:31 PM, Mark Thomas wrote:
AH NF wrote:
Hi all,
Ok so I have my ROOT.war and "/" host all w
AH NF wrote:
Hi all,
Ok so I have my ROOT.war and "/" host all working as I would like.
I startup tomcat with no application defined, and go to /manager. I
upload my ROOT.war file,tomcat places it in myAppBase/ROOT as expected.
The application boots
up OK.
My only problem is that Tomcat appea
hes (maybe trying to load 0-ROOT & 1-ROOT)
On Feb 27, 2008, at 10:20 AM, Caldarale, Charles R wrote:
From: ahnf [mailto:[EMAIL PROTECTED]
Subject: totally confused! deploy & redeploy the ROOT context
via manager app and/or ant
Have a custom virtual host called "myApp"
otally confused! deploy & redeploy the ROOT context
via manager app and/or ant
Have a custom virtual host called "myApp", this host will run
one web-application, and that web application should respond
at the "/".
Stop trying to do things the hard way, and just package your d
> From: ahnf [mailto:[EMAIL PROTECTED]
> Subject: totally confused! deploy & redeploy the ROOT context
> via manager app and/or ant
>
> Have a custom virtual host called "myApp", this host will run
> one web-application, and that web application should respond
Hi,
I've spent the last day trying to do this with no success and here is what I
would like to do:
What I want to be able to do
--
Have a custom virtual host called "myApp", this host will run one
web-application, and that web applicati
> From: osubb [mailto:[EMAIL PROTECTED]
> Subject: RE: Configuring Default ROOT Context
>
> I was just going to use the Default context for
> development.
The conf/context.xml file is *not* the default context. Instead, that
file specifies a set of default attributes to be
Thanks for the help. I was just going to use the Default context for
development. But I can do it the correct way.
osubb
Caldarale, Charles R wrote:
>
>> From: osubb [mailto:[EMAIL PROTECTED]
>> Subject: RE: Configuring Default ROOT Context
>>
>> I unco
> From: osubb [mailto:[EMAIL PROTECTED]
> Subject: RE: Configuring Default ROOT Context
>
> I uncommented the "invoke servlet" sections in web.xml
Don't ever, ever do that; read the comments about the Invoker servlet in
the FAQ:
http://wiki.apache.org/tomcat/FAQ/Mi
I got the servlet reload to work, but can't get the default ROOT context to
work.
I uncommented the "invoke servlet" sections in web.xml and when I executed
any Servlets, I got a blank page.
I then commented them back out, and the Servlet worked fine (although I
could not exe
> From: osubb [mailto:[EMAIL PROTECTED]
> Subject: Configuring Default ROOT Context
>
> I have a book that is about 4 years old
Throw it away. It will have little bearing on current practice.
All of the topics you're posting about have been complete redone. Read
the c
o add
some code ''. But I could never find the
sentence when doing a search in server.xml.
2) I would like to enable the ROOT context. It says to uncomment the line
'', but again, I can't find this
line in server.xml.
Any help would be great!
osubb
--
View
Sorry I overlooked some previous conversation.
On 9/18/07, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
>
> > From: Waseem Azhar [mailto:[EMAIL PROTECTED]
> > Subject: Re: Changing ROOT context
> >
> > Just open your server.xml add line > docBase="y
> From: Waseem Azhar [mailto:[EMAIL PROTECTED]
> Subject: Re: Changing ROOT context
>
> Just open your server.xml add line docBase="your-app-name" debug="99" reloadable="true"/>
Please read the doc before responding. Putting elements in
server.
i,
>
> I have a problem with changing the default ROOT context to something else
> (myroot).
>
>
> Specs
> -Windows Vista
> -Tomcat 6.0.14 (latest)
>
>
> Problem
> I want the following directory to be the ROOT context:
> $CATALINA_HOME/w
> From: StrongGorilla [mailto:[EMAIL PROTECTED]
> Subject: Re: Changing ROOT context
>
> I downloaded the Servlet Spec 2.5 pdf, but it says nothing
> about "ROOT".
Correct; the name ROOT is Tomcat's way of denoting the default context,
replacing the older path=
> From: StrongGorilla [mailto:[EMAIL PROTECTED]
> Subject: RE: Changing ROOT context
>
> Strange that is it possible when I define to context
> in server.xml, but not possible when I define it in
> conf/catalina/localhost/ROOT.xml
I suspect that the webapp was deployed
? The servlet spec is very clear that the
> ROOT webapp is a special webapp accepting all requests that do not match
> any other web application context.
>
> --David
>
> FastGorilla wrote:
>> Hi,
>>
>> I have a problem with changing the default ROOT con
Strange that is it possible when I define to context in server.xml, but not
possible when I define it in conf/catalina/localhost/ROOT.xml
Caldarale, Charles R wrote:
>
>> From: FastGorilla [mailto:[EMAIL PROTECTED]
>> Subject: Changing ROOT context
>>
>> How can I
:
>> Hi,
>>
>> I have a problem with changing the default ROOT context to something else
>> (myroot).
>>
>>
>> Specs
>> -Windows Vista
>> -Tomcat 6.0.14 (latest)
>>
>>
>> Problem
>> I want the followin
> From: FastGorilla [mailto:[EMAIL PROTECTED]
> Subject: Changing ROOT context
>
> How can I change ROOT to myroot, and let
> http://localhost:8080/test.txt be the url?
You can't - the default context must be named ROOT. Just rename your
webapp, as others have suggest
have you tried to create a file called ROOT.xml in
conf/Catalina/localhost containing your tag?
(of course, remove webapps/ROOT first)
Filip
FastGorilla wrote:
Hi,
I have a problem with changing the default ROOT context to something else
(myroot).
Specs
-Windows Vista
-Tomcat
problem with changing the default ROOT context to something else
(myroot).
Specs
-Windows Vista
-Tomcat 6.0.14 (latest)
Problem
I want the following directory to be the ROOT context:
$CATALINA_HOME/webapps/myroot
So that http://localhost/test.txt is directly mapped to
Hi,
I have a problem with changing the default ROOT context to something else
(myroot).
Specs
-Windows Vista
-Tomcat 6.0.14 (latest)
Problem
I want the following directory to be the ROOT context:
$CATALINA_HOME/webapps/myroot
So that http://localhost/test.txt is directly
> From: Tent Pig [mailto:[EMAIL PROTECTED]
> Subject: RE: Configuring TOMCAT to use different ROOT context
>
> The problem I'm encountering is a request to:
> http://path/to/sectionx/test.jsp
> will yield an error 400, bad request.
Are you sure it's even getting to
--- "Caldarale, Charles R"
<[EMAIL PROTECTED]> wrote:
> I hope you're more careful with proper casing than
> the above would lead us to believe. If the above is
> really what you put in, it would have no
> effect, since both the element and attributes are
> incorrect.
My casing is AFAIK correct
> From: Tent Pig [mailto:[EMAIL PROTECTED]
> Subject: RE: Configuring TOMCAT to use different ROOT context
>
> I put in tomcat's server.xml:
>
> />
I hope you're more careful with proper casing than the above would lead
us to believe. If the above is really wh
--- "Caldarale, Charles R"
<[EMAIL PROTECTED]> wrote:
> Can you use Tomcat's multiple capability to
> accomplish this segregation? Each element
> has its own appBase, which could point to the
> appropriate DocumentRoot directory for the
> corresponding httpd virtual host.
Well, I tried this.
> From: Tent Pig [mailto:[EMAIL PROTECTED]
> Subject: Configuring TOMCAT to use different ROOT context
>
> Plus, she has different JSP pages for each virtual
> host and doesn't want to 'mix and match' them. In
> other words, if 'myfile.jsp' is only av
Hi everyone.
I'm sorry if this seems like a newbie question,
unfortunately I'm a complete neophyte when it comes to
tomcat setup and configuration.
I have a user who manages website content, setup and
administration of the linux server falls upon me. On
this web server my user has several website
ou
can still access the Tomcat app at http://localhost:8080/ , and your
app at http://virtual-host-for-your-app:8080/
then both apps will be on the root context.
Or you could switch the default Tomcat app to it's own virtual host as
http://tomcatapp:8080/ and keep localhost for your a
en they would probably get too many "tomcat is
broken" queries.
have fun...
- Original Message -
From: "Srinivas V." <[EMAIL PROTECTED]>
To:
Sent: Monday, April 09, 2007 10:43 PM
Subject: Questions about ROOT context
Hello tomcat experts
I'm working on a
There's no problem with using ROOT , it just means that your
application will be accessible from the ROOT context , instead of
another context.
ROOT context means you can access the app at http://localhost:8080/
< the slash is root.
If you deploy your app at another context then
Hello tomcat experts
I'm working on a new tomcat based website. I will be manager the server
entirely and so will be the only person deploying html/jsp/servlets to it.
I've been reading a few books and they suggest using custom webapps instead
of the ROOT one. But I haven't seen any hard reasons
> From: Jim Goodspeed [mailto:[EMAIL PROTECTED]
> Subject: Re: Root context setup
>
> Should I delete the contents of this directory everytime I
> deploy a new war file?
I don't really know if it's required, but I always do (or rather, the
deployment script alway
> From: Jim Goodspeed [mailto:[EMAIL PROTECTED]
> Subject: Re: Root context setup
>
> Is there another way to accomplish this though?
Don't put the .war file in Tomcat's directory structure. Instead, put a
ROOT.xml file in conf/Catalina/[hostname] that contains a
element w
> From: Jim Goodspeed [mailto:[EMAIL PROTECTED]
> Subject: Re: Root context setup
>
> Is there another way to accomplish this though?
Don't put the .war file in Tomcat's directory structure. Instead, put a
ROOT.xml file in conf/Catalina/[hostname] that contains a
Thanks Hassan.
Is there another way to accomplish this though? I would really like to keep
the name of the war file to the name of the application. We have several
different apps and it would be much easier from a organizational point of
view if we were able to customize the name of the war fil
On 2/16/07, Jim Goodspeed <[EMAIL PROTECTED]> wrote:
I want myapp.war to be the default application
Name it ROOT.war, which Tomcat recognizes as the default context.
HTH,
--
Hassan Schroeder [EMAIL PROTECTED]
--
1 - 100 of 124 matches
Mail list logo
