No need to apologize - learning requires making mistakes and I
appreciate the responses that you and David Smith gave in pointing me in
the right direction. I've got some work to do but I now understand much
better that I was getting away with something for quite some time and
shouldn't have b
Scott Dunbar wrote:
> I want a directory to be the root directory of a virtual host. That
> directory is itself a webapp and may have other directories within it
> that are webapps (with explicit Context elements).
You simply can't do this. Tomcat was never intended to work this way.
As I said be
The organization of webapps isn't tree oriented on disk. It's a flat
list of webapps on disk with the "default" webapp being named the
special name ROOT (defined by the servlet spec). If you need webapps
organized deeper than the top level (ie /myWeb/path/app), then you use
the pound symbol a
Thanks for the input. However, I guess I'm still missing something.
I want a directory to be the root directory of a virtual host. That
directory is itself a webapp and may have other directories within it
that are webapps (with explicit Context elements). To this point I have
never had to
Scott Dunbar wrote:
> Thanks, I checked that and my I don't set a docBase in my context:
>
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
>
>
And there is the problem. If it isn't absolute, docBase is relative to
ap
Thanks, I checked that and my I don't set a docBase in my context:
...
This exact same server.xml works fine under 5.5.15 which I've been
running for about 16 months. I'll keep digging but after being bit by a
bug in 5.5.16 I need to be much more careful with upgrading to new
T
Scott Dunbar wrote:
> I've been using the same code for years since the Tomcat 3.x days and an
> upgrade to 5.5.23 has now broken my site.
Check your config for appBase in a host element being set to the same
directory as the docBase for a context. Most likely this will be in a
ROOT context for th
On 5/7/07, Scott Dunbar <[EMAIL PROTECTED]> wrote:
I've been using the same code for years since the Tomcat 3.x days and an
upgrade to 5.5.23 has now broken my site.
I would safely assume there have been significant changes between 3.x
and 5.5.23, if I were you I would start fresh, also the ins
I've been using the same code for years since the Tomcat 3.x days and an
upgrade to 5.5.23 has now broken my site.
If I do a:
I get:
The requested resource (/some/path/to/some.html) is not available. It
is available and this particular file hasn't been modified for a very
long time. If I
