In article <[EMAIL PROTECTED]>, Craig R. McClanahan
<[EMAIL PROTECTED]> writes
>Tomcat does not support servlet chaining like JWS does, and there are no plans
>to add it -- this design pattern turns out to be fraught with problems.
That is a shame, servlet chaining is such a powerful tool. If you have
time could you explain some of the problems, after all JWS and
ServletExec from Newatlanta seem to show it can work. Perhaps it allows
developers to mess things up to easily, or it compromises security? Or
perhaps there are problems with JWS and ServletExec that I haven't come
across yet.
> contents to the response unmodified. (After all,
> that is all the default file-serving servlet does :-).
Yes, ServletExec supports chaining, but it doesn't have the equivalent
of the file servlet so I have implemented that already.
>* Set up a new web application, mapped to the name
> of your directory, and with a document root pointing
> at that directory. Now, put the configuration stuff
> above in the web.xml file for the new web application.
> The filtering will only be done for HTML files within that
> directory -- all others will be handled in the usual way.
I like that!
Craig, thanks for a very helpful reply, it wasn't exactly what I wanted
to here, but your other solutions seem to be flexible to do what I need
to do.
Regards,
David
--
David M. Smith
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
