Re: Default context for web app

2003-12-17 Thread Adam Hardy
On 12/17/2003 12:39 AMnbsp;Kent Boogaart wrote: Didn't work. So I can't do what you're doing. Strange. Are you dead certain you don't have an /eSM/ context? Adam Hi Adam, It's a bit hard to tell for certain since I have disabled the manager app. However, I can tell you that there is only one

Re: Default context for web app

2003-12-16 Thread Adam Hardy
On 12/16/2003 12:00 AMnbsp;Kent Boogaart wrote: When I do that, I get a context at / and a context at eSM. In $TOMCAT_HOME/work/Standalone/localhost/ tomcat makes both _ and eSM. I use exactly the same context config as you, except some I don't declare since the defaults are the same. The only one

Re: Default context for web app

2003-12-16 Thread Adam Hardy
On 12/16/2003 10:15 AMnbsp;Adam Hardy wrote: I'll experiment: if I put all my context info in the server.xml, then maybe it will work. Didn't work. So I can't do what you're doing. Strange. Are you dead certain you don't have an /eSM/ context? Adam -- struts 1.1 + tomcat 5.0.16 + java 1.4.2

Re: Default context for web app

2003-12-16 Thread Kent Boogaart
Didn't work. So I can't do what you're doing. Strange. Are you dead certain you don't have an /eSM/ context? Adam Hi Adam, It's a bit hard to tell for certain since I have disabled the manager app. However, I can tell you that there is only one directory below work/Standalone/localhost and it

Re: Default context for web app

2003-12-15 Thread Kent Boogaart
When I do that, I get a context at / and a context at eSM. In $TOMCAT_HOME/work/Standalone/localhost/ tomcat makes both _ and eSM. I use exactly the same context config as you, except some I don't declare since the defaults are the same. The only one I don't recognise is 'displayName' - can't see

Re: Default context for web app

2003-12-12 Thread Adam Hardy
On 12/12/2003 12:15 AM Kent Boogaart wrote: I am currently running against version 4.1.27 of Tomcat. I did not alter the name of my deploy directory. Here is my Context element (with env entries removed): Context className=org.apache.catalina.core.StandardContext cachingAllowed=true

RE: Default context for web app

2003-12-11 Thread Shapira, Yoav
context for web app Wow - thanks for all the help people. Just thought I'd update you on how I resolved this. Firstly, I removed all Context elements from conf/server.xml except my own. Then I set autoDeploy to false on the Host element. This almost got everything working as required. However

Re: Default context for web app

2003-12-11 Thread Adam Hardy
On 12/11/2003 12:51 AM Kent Boogaart wrote: Wow - thanks for all the help people. Just thought I'd update you on how I resolved this. Firstly, I removed all Context elements from conf/server.xml except my own. Then I set autoDeploy to false on the Host element. This almost got everything working

Re: Default context for web app

2003-12-11 Thread Kent Boogaart
Hi Adam, I am currently running against version 4.1.27 of Tomcat. I did not alter the name of my deploy directory. Here is my Context element (with env entries removed): Context className=org.apache.catalina.core.StandardContext

Re: Default context for web app

2003-12-10 Thread Adam Hardy
On 12/10/2003 08:53 AM Kent Boogaart wrote: Hi all, I am trying make my web application available via the default context. In other words, when I type http://localhost:8080/ in a browser on the local machine I want my web app to appear rather than the Tomcat default web app. I figured I'd just

RE: Default context for web app

2003-12-10 Thread Shapira, Yoav
ChemInformatics -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 6:48 AM To: Tomcat Users List Subject: Re: Default context for web app On 12/10/2003 08:53 AM Kent Boogaart wrote: Hi all, I am trying make my web application available via

Re: Default context for web app

2003-12-10 Thread Ben Souther
If you've manually deployed your app and it's the only one running in that server, you could turn off autoDeploy from the host node in your server.xml file. Then Tomcat would only deploy the apps that you've specifically set up context elements for. -Ben Host name=localhost

Re: Default context for web app

2003-12-10 Thread Adam Hardy
-string-path context. Yoav Shapira Millennium ChemInformatics -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 6:48 AM To: Tomcat Users List Subject: Re: Default context for web app On 12/10/2003 08:53 AM Kent Boogaart wrote: Hi all, I am

RE: Default context for web app

2003-12-10 Thread Shapira, Yoav
Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 9:07 AM To: Tomcat Users List Subject: Re: Default context for web app Yoav, from my brief experiment, if you don't place it in ROOT, then like the Kent said it gets deployed twice. e.g. I put my app in APPBASE

[OT] Re: Default context for web app

2003-12-10 Thread Graham Reeds
Howdy, It's deployed twice if you also have autoDeploy enabled. ROOT has NOTHNING special. Maybe for the next release we should change the name ROOT to something else just so people stop thinking there's something special about it ;) SHRUB? Blame Monty Python. G.

Re: Default context for web app

2003-12-10 Thread Adam Hardy
] Sent: Wednesday, December 10, 2003 9:07 AM To: Tomcat Users List Subject: Re: Default context for web app Yoav, from my brief experiment, if you don't place it in ROOT, then like the Kent said it gets deployed twice. e.g. I put my app in APPBASE/gargantus/ and set the context xml: path

RE: Default context for web app

2003-12-10 Thread Shapira, Yoav
-Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 10:02 AM To: Tomcat Users List Subject: Re: Default context for web app At risk of getting you totally exasperated :0 , I beg to differ. If I have no context entries in server.xml

Re: Default context for web app

2003-12-10 Thread Kent Boogaart
Wow - thanks for all the help people. Just thought I'd update you on how I resolved this. Firstly, I removed all Context elements from conf/server.xml except my own. Then I set autoDeploy to false on the Host element. This almost got everything working as required. However, the admin and manager