First, let me clarify that I am only a user of Tomcat and was simply
pointing out the part of the documentation.
Now as for the issue, I am not sure that it is a bug but just a feature.
Unless you can show where it does not meet the servlet specs then it will
not be considered a bug.
I am not sure why this is causing such a problem. The only time a default
context will ever be used is if the browser is using an IP instead of a URL
or if you have a DNS entry that points to your IP with no matching
application.
So unless you are using only the IP or are directing multiple unmatched URLs
at the server there is no issue. If you are, then knowing what the war is
about is only a small piece of the puzzle that exist in the setup.
Just my understanding of the setup. Feel free to enlighten me if you think I
am off base.
Every aspect of a program is considered a feature. No matter how good or bad
one may think it is. It only become a bug when it breaks a rule. Either the
programmers rule, a system rule or a specification rule.
If a feature that was considered bad by some could be classed as a bug, then
90% of the code written in the world would be bugs because somewhere there
is someone who doesn't like it.
Doug
----- Original Message -----
From: "Thomas Corte" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Sent: Tuesday, August 30, 2005 4:28 PM
Subject: Re: "No Host matches server name localhost" error
Hi,
Parsons Technical Services wrote:
Per the 5.5 doc you can't do it that way. You can only specify the path
as a blank string when the context element is in the server.xml.
To reiterate: so the only 2 ways to define the *default web app* for the
host are either
- to define the context in server.xml (which is inconvenient because it
may e.g. contain JNDI resource definitions that have to be updated
whenever META-INF/context.xml within the war changes)
or
- to name the war file for the default webapp "ROOT.war"
(which is somewhat crappy, too, since it e.g. leaves no hint
at what the war is about if someone just looks at the webapps drawer)
If the above is true, I wonder why the path attribute of the context
defined in META-INF/context.xml isn't simply considered in *any* case?
Shouldn't this be considered a tomcat bug?
--
Thomas Corte
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
