extra one of these underneath your newest Context
tag you added.
-Original Message-
From: richhse [mailto:[EMAIL PROTECTED]
Sent: Monday, January 28, 2008 9:48 AM
To: users@tomcat.apache.org
Subject: Re: Context does not work
Can I just follow up a point that was made earlier on as I am h
, January 28, 2008 9:48 AM
To: users@tomcat.apache.org
Subject: Re: Context does not work
Can I just follow up a point that was made earlier on as I am having a
similar issue:
I am using tomcat 4.1:
I have defaultContext and all works fine.
If I try to add a context as below to server.xml on a fedora
mcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Context-does-not-work-tp14839818p15138139.html
Sent from the Tomcat - User mailing list archive at Nab
> Yes, it's very bad style - don't do it. Unless you need some special
> settings for the attributes, you don't really need a
> element at all. For your case just name your .war file (or the expanded
> directory under webapps) "welcome" and you'll have what you want.
>
Hey Chuck, thanks for t
> A second launch means a second set of servlet instances, second set of
> resources, overall a higher memory footprint and they won't share data.
>
> Placing this stuff in server.xml does work, but if you want to change
> the config you are required to bounce the tomcat service for changes to
> ta
> From: Chris Riekenberg [mailto:[EMAIL PROTECTED]
> Subject: Re: Context does not work
>
> Can you explain this a little bit more detailed? What does a secon
> launch mean?
It means you get two webapps started, one with the path "welcome", one
with a path that'
A second launch means a second set of servlet instances, second set of
resources, overall a higher memory footprint and they won't share data.
Placing this stuff in server.xml does work, but if you want to change
the config you are required to bounce the tomcat service for changes to
take effe
> So you want you make your webapp to also respond at
> http://[myServer:port]/welcome. You can achieve a second launch of your
> webapp just by placing welcome.xml (w/ your Context config) in
> [TomcatHome]/conf/Catalina/localhost. Just know this is a second
> launch, not an alias to the first r
Chris Riekenberg wrote:
Hmm... might help to define "But it doesn't work." How exactly does it
not work?
He returns a Http error 404. Page could not find.
For the record, you Context element should *not* be in
conf/context.xml. That file defines defaults for all webapps. It
*sh
> Hmm... might help to define "But it doesn't work." How exactly does it
> not work?
>
He returns a Http error 404. Page could not find.
> For the record, you Context element should *not* be in
> conf/context.xml. That file defines defaults for all webapps. It
> *should* be in one of two place
Hmm... might help to define "But it doesn't work." How exactly does it
not work?
For the record, you Context element should *not* be in
conf/context.xml. That file defines defaults for all webapps. It
*should* be in one of two places:
webapps/StrutsDemo/META-INF/context.xml in which case
Hey,
I'm using Tomcat 5.5.12. If I created a context mapping in
/conf/server.xml to cnetext /welcome.
If I do it like this, it works. But I read, that you should not
insert a mapping in server.xml (bad style?) You should prefer
to insert it into
/conf/context.xml
or
\conf\Catalina\localhost\.xm
12 matches
Mail list logo
