The stack is to accommodate the geniuses who have a Servlet in /appA that includes one in /appB which in turn includes another in /appA.
In that case the servlet gets called directly by the request dispatcher, without going through StdWrapperValve.invoke. So there isn't any extra wrapping that I can see.
Using the call hierarchy feature in Eclipse, I see it could be stacked if loading the servlet as a result of a request dispatcher call. Swallowing output during servlet lifecycle operations is, IMO, not really worth adding all that complexity (although I don't care: I'm not using the feature).
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
