This is a good discussion.
I would like to introduce the question: How much work is it to undo the platform
dependency, and is it worth the liability to take advantage of a nice feature of
the server?
Specifically, would the interceptor approach offer significant benefits over the
Servlet adapter approach? And how much work would it involve (potentially) to
adapt the interceptor approach to some other unnamed platform if needed?
-Erik
"Pier P. Fumagalli" wrote:
> Filip Hanik at [EMAIL PROTECTED] wrote:
>
> > For Tomcat 3.x, you can create an interceptor to act as a startup class.
> > you can just configure it using the server.xml file, read more about this in
> > http://www.filip.net/tomcatbook/TomcatInterceptors.html
>
> Again, this would be unportable to other containers... My reasoning is that
> Erik needs some functionality for a web application that will allow his code
> to be 100% portable on all possible servlet containers.
>
> Using tomcat interceptors is exactly like using Weblogic's startup classes,
> unportable. That's why I'm not a fan of interceptors (or valves in Tomcat
> 4.0), or ANY other unportable feature.
>
> Pier
