RE: TC33b1 Context path behavior: Is this a bug or by design?

2001-08-06 Thread Larry Isaacs
Randall, It is the path of the context that makes them unique. So, Context path=/struts-documentation ... / would replace the auto-served context, where: Context path=/strutsdoc ... creates a new context. The fact that its docbase is the same as the one for the /struts-documentation

RE: TC33b1 Context path behavior: Is this a bug or by design?

2001-08-06 Thread Larry Isaacs
Please ignore. Didn't see the other discussion that already deal with this issue. -Original Message- From: Larry Isaacs [mailto:[EMAIL PROTECTED]] Sent: Monday, August 06, 2001 9:26 AM To: '[EMAIL PROTECTED]' Subject: RE: TC33b1 Context path behavior: Is this a bug or by design?

Re: TC33b1 Context path behavior: Is this a bug or by design?

2001-08-05 Thread cmanolache
Hi Randall, I believe the behavior is correct - you have 2 contexts with the same docbase ( one defined in a config file, one automatically ). They are completely independent of each other ( you can look into work and you'll see one work dir for each ). If you write a simple test servlet, you'll

Re: TC33b1 Context path behavior: Is this a bug or by design?

2001-08-05 Thread Randall Parker
On Sun, 5 Aug 2001 00:30:03 -0700 (PDT), [EMAIL PROTECTED] wrote: Hi Randall, I believe the behavior is correct - you have 2 contexts with the same docbase ( one defined in a config file, one automatically ). So is there a way to turn off the creation of that automatic context? I'd also like

Re: TC33b1 Context path behavior: Is this a bug or by design?

2001-08-05 Thread Rob S.
So is there a way to turn off the creation of that automatic context? I'd also like a way to say If a Context tag is defined then do not also generate an automatic context. The name of the path attribute and the name of the dir in /webapps have to be the same. You can rename one or the

Re: TC33b1 Context path behavior: Is this a bug or by design?

2001-08-05 Thread cmanolache
On Sun, 5 Aug 2001, Randall Parker wrote: So is there a way to turn off the creation of that automatic context? Remove AutoDeploy src=webapps / to disable all automatic contexts ( from webapps ). Move the app out of webapps. AutoDeploy takes all the files from the specified dir and add them.

Re: TC33b1 Context path behavior: Is this a bug or by design?

2001-08-05 Thread Randall Parker
Costin, If one does define a context in apps-.xml can one sent context-param tags in it that are then accessible as part of that ServletContext? More generally, can anything from webl.xml be put in server.xml inside a Context tag's scope? See for example the context-param below where

Re: TC33b1 Context path behavior: Is this a bug or by design?

2001-08-05 Thread cmanolache
On Sun, 5 Aug 2001, Randall Parker wrote: Costin, If one does define a context in apps-.xml can one sent context-param tags in it that are then accessible as part of that ServletContext? More generally, can anything from webl.xml be put in server.xml inside a Context tag's scope?

Re: TC33b1 Context path behavior: Is this a bug or by design?

2001-08-05 Thread Randall Parker
On Sun, 5 Aug 2001 10:48:31 -0700 (PDT), [EMAIL PROTECTED] wrote: More generally, can anything from webl.xml be put in server.xml inside a Context tag's scope? No, and that's premeditated :-) Okay. Keep in mind server.xml ( and apps.xml ) is an ad-hoc format, and just one of the ways to