: There lies the problem i don't know which servlets i would get, and i don't
: want to reconfigure the web.xml and restart the server every time something
: changes or get added.

If you want changes to be picked up w/o restarting the server, you'll
have to set "reloadable=true" for the context, which could lead to
performance issues.


: We are using a database to store the mapping of urls to servlets.
: I think web.xml would be pretty confusing if I register all my 200 Servlets in
: it.

If you're using a database to hold your servlet mappings, you could
write a program to extract that data and generate web.xml for you.

What about migrating those servlets to JSPs? In an exploded WAR file,
new/changed JSPs are picked up automatically.

I realize that's more of long-term fix, but if you have 200+ servlet
mappings and don't want to work with the spec-standard deployment
descriptor, your options are few.

-QM

--

software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)