wood burning stoves 2.0*
The moose likes Servlets and the fly likes Chaining/Filtering 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 » Java » Servlets
Bookmark "Chaining/Filtering" Watch "Chaining/Filtering" New topic
Author

Chaining/Filtering

Kev D'Arcy
Ranch Hand

Joined: Jul 26, 2001
Posts: 75
I've been thinking about this for the last few days and can't decided what to do! ANy input would be appreciated! I want to have a single servlet that sits in front of all other servlets in my application (kind of a web service type app). This servlet should inspect incoming request and decide to process it if it's from a valid source, or kick it out if not. If it's valid, then it should inspect some XML (will probably have to parse it) and depending on it's content, log it and forward it to another "worker" servlet. But my problem is that while I want my servlet to do all this work, I want it to be lightweight. Filtering isn't an option as my app server doesn't support it (wakey wakey IBM!). Any thoughts???
 
Consider Paul's rocket mass heater.
 
subject: Chaining/Filtering
 
Similar Threads
allowing only certian urls access to web app
Filters and ErrorPages
How to capture response sent from a website
is web.xml compulsory
Hiding URL from source