Howdy,
and this is my context (which is found in META-INF/context.xml):
Context path= docBase=gargantus.war cachingAllowed=false
reloadable=false
Anybody else with the same setup see this? Bug or not bug?
snip/
Seems like a bug. What happens if you don't have context.xml at all in
your
On 02/09/2004 02:58 PM Shapira, Yoav wrote:
and this is my context (which is found in META-INF/context.xml):
Context path= docBase=gargantus.war cachingAllowed=false
reloadable=false
Anybody else with the same setup see this? Bug or not bug?
snip/
Seems like a bug. What happens if you don't
Howdy,
If there's no context.xml, then I don't get a root context - no _, no
nada - and no errors. Just the context with the same name as the war
file.
So if there's no context.xml, the behavior is correct (with all default
values, e.g. reloadable). If you add a context.xml, you get the
On 02/09/2004 11:01 PM Shapira, Yoav wrote:
If there's no context.xml, then I don't get a root context - no _, no
nada - and no errors. Just the context with the same name as the war
file.
So if there's no context.xml, the behavior is correct (with all default
values, e.g. reloadable). If you
I definitely have the same problem. And Tomcat does not execute context.xml.
I presume is due to the error message: context already in use.
Do you have the some problem?
Hernani
-Original Message-
From: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: sabado, 7 de Fevereiro de 2004 12:47
To:
I get no error message - I just grepped the log file. For me the problem
is totally benign - unless I decide that I want to have a context with
the same name as my root context's war file.
I suggest that you are getting an error because you have doubled the
Context somehow - perhaps you still
