This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes Tomcat and the fly likes Getting /servlet/* to work in Tomcat without explicitly putting invoker Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Getting /servlet/* to work in Tomcat without explicitly putting invoker" Watch "Getting /servlet/* to work in Tomcat without explicitly putting invoker" New topic
Author

Getting /servlet/* to work in Tomcat without explicitly putting invoker

Chase Bonham
Ranch Hand

Joined: Jul 15, 2006
Posts: 50
Getting /servlet/* to work in Tomcat without explicitly putting invoker
in web.xml

I looked around on the web for the answer to this question. Other than the option of enumerating each and every servlet in the web.xml, I haven't seen
any solution.
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 60789
    
  65

What would be the difference between enabling the invoker or writing one yourself?

If you don't want to list each servelt in the deployment descriptor, you might want to explore the Front Controller pattern. This article may be helpful.


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Getting /servlet/* to work in Tomcat without explicitly putting invoker
 
Similar Threads
everything dandy except servlet
deployement of a simple servlet
Problem in simple Filter servlet Program
Cannot run servlet
Getting started with JSP-Servlet using apache-tomcat-5.5.17