On Monday 10 November 2003 6:26 pm, Tim Funk wrote:
> Few options ...
> 1) Place each group in its own virtual host. Then register a manager app
> per virtual host.
Hi,
I'm looking at this again. The manager is a servlet container application (as
I gather it's called) and is in server/webapps/m
Few options ...
1) Place each group in its own virtual host. Then register a manager app per
virtual host.
2) Write a filter and add that to the manager web.xml to perform the extra
acl needs
3) Write a perl(or pick your fav lang) wrapper that does all the ACL work
then it calls the manager app
Hi!
I'm looking for ideas, conventions, or standard approaches to giving people
control over Tomcat Manager operations that are specific to particular
applications. This could involve virtual hosts, realms, and such, but I want
to avoid setting up multiple servers, JVMs and such.
I would like
