> From: Terence Kent [mailto:[EMAIL PROTECTED]
> Subject: Re: servlet mapping question(I believe)
>
> In my case I have multiple applications in the webapps
> folder, so which to name to root is ambiguous.
The one to name ROOT (not root) is the one you want clients to see when
th
On Feb 3, 2008, at 10:58 AM, Konstantin Kolinko wrote:
Konstanin,
Thank you for your response! Below are responses to your statements...
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd";>
Why are you using such an old version of specification? Why not 2.4
or 2.5??
I think my question was m
Mark,
Thank you very much! Your suggestion worked perfectly and has given me
an area to focus on.
Terence.
On Feb 3, 2008, at 10:51 AM, Mark Thomas wrote:
Terence Kent wrote:
Conclusion:
My understanding from this configuration is that all requests on
port 8010, that end with the extensi
>"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd";>
Why are you using such an old version of specification? Why not 2.4 or 2.5??
Nowadays, with tomcat 5.5 and 6.0 it is very rare (and discouraged) to
configure context in server.xml.
For the root application it is sufficient to name it "ROOT"
Terence Kent wrote:
Conclusion:
My understanding from this configuration is that all requests on port
8010, that end with the extension .ext should be forwarded to the
servlet "mycompany". From what I've read, any paths created in the
${APP_BASE} directory should be irrelevant in this mapping
Hello all,
I am new to tomcat and running into a problem that I am unable to
resolve. I don't know all the correct vocabulary to use here, so bare
with me as I attempt to describe the problem I'm running into. Here
goes...
In a nutshell:
All requests to:
dwww.mycompany.com:8010/foor/bar.
