Paul Hoffman wrote:My servlet hosting provider however has me use the virtual directory name of 'servlet' to access the servlet (for example, http://www.mydomain.com/servlet/TheServlet
So your hosting provider is pushing you to use the InvokerServlet of their
Tomcat machine?
Bad idea. I would look for another hosting provider. If that is really not an option, you could consider creating a Filter to 'mask' the URL. But again, this isn't a good idea. I also have never seen a hosting provider which does so. This makes namely no sense.
Why did they push you to do so? Were you encountering problems and were you asking them for help and did the one probably not understand the other or so? What hosting provider is it by the way? How do you deploy webapps to there? As a WAR? Or isn't that allowed either? Well, OK, then I can understand the need for InvokerServlet. I would still look for a better hosting provider where you can deploy WAR's.