No, all that happens if you write your webapp as ROOT make the <Context
path=""/> in context.xml and dump it into web-apps is that your jsp pages
will now show instead of the default tomcat page http://localhost:8080
In fact I think that somewhere on that page it tells you , you can do
precisely this.
And yes its a cool way to then point at all you other applications and
servlets... just got remember that now there is no cool page that lets you
click on the manager, and so you have to type
http://localhost:8080/manager/html
to get to the manager.
Nothing breaks.... so yes take the core domain name back from the helpful
tomcat page... thats all it does.... lets you get around without remembering
urls... and you going to want to do that for your users. Yes maybe they
should have done it like this http://localhost:8080/tomcat/developers
and left ROOT empty... but then they would probably get too many "tomcat is
broken" queries.
have fun...
----- Original Message -----
From: "Srinivas V." <[EMAIL PROTECTED]>
To: <users@tomcat.apache.org>
Sent: Monday, April 09, 2007 10:43 PM
Subject: Questions about ROOT context
Hello tomcat experts
I'm working on a new tomcat based website. I will be manager the server
entirely and so will be the only person deploying html/jsp/servlets to it.
I've been reading a few books and they suggest using custom webapps
instead
of the ROOT one. But I haven't seen any hard reasons as to why I can't use
ROOT for all my stuff. If the server was used by multiple teams/groups by
a
common admin, then I can see the value in having separate webapps. But for
my use-case, is there any problem with just using ROOT ?
thanks
Srinivas
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
