2009/2/6 Robert Koberg <r...@koberg.com>: >>> Which is a good reason not to use a valve. Unless you need access to >>> Tomcat internals, use a filter. >> >> ? Unclear why Charles? >> >> To make it 'filter' all server traffic? >> AFAIK I don't need access to any internals. > > You seem to be making this much more complicated than it needs to be. First, > if you really need your templates to be secure, this won't solve the problem > because someone can easily duplicate your client. And if you don't /really/ > need it secure, why do it?
Only one aspect of security Rob. As needed I'll look at others later. Can you suggest alternatives to achieve what I want, rather than something else? > > If you do need it secure, why not just use a security constraint. If there > are just a few people that need to access the templates, you could use the > default tomcat-users.xml setup - easy. Not what I'm asking for. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
