Win a copy of Cloud Native PatternsE this week in the Cloud forum
or Natural Language Processing in the AI/ML forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
  • Paul Clapham
  • Knute Snortum
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Piet Souris
  • Stephan van Hulst
  • Carey Brown
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

the invoker servlet blues ~hamonica rift~

Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I've taken over work on an instance of Tomcat which runs two seperate applications.

Previously, one app resided under ROOT and used the invoker servlet for it's servlets. The second (developed later) resides in it's own context.

This setup has caused numerous issues which I've resolved by moving the first application to it's own context.

However, now that I've done that, numerous client applications with hardcoded URLS (yes, ugh) have broken since they're looking for the old servlets which ran under the invoker servlet.

What is the best way to remedy this? I do not want anything running under the invoker servlet.

Should I:

A. Create a middle man servlet that sits in ROOT and simply redirects the request to the correct location (and relays the response).


B. Is it possible to configure Tomcat to do this for me?


maps to ==>

TIA for any suggestions,
Consider Paul's rocket mass heater.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!