Gael Marziou wrote:
Solution may depend on which criteria you use to determine whether you
should enable or disable a feature.
Without knowing more on your requirements, I would use a servlet
controller and JAAS permissions granted per role or subject in order to
enable/disable features.
I would like an interface like this:
---------------------
Cake Servlet [X]
Coffee Servlet [ ]
Fruit Servlet [X]
|OK| |Cancel|
---------------------
Each configuration maps to a servlet. I don't need access control or
grant a specific user access to a feature. If the user deselects the
"Cake Servlet" I want that Servlet to become unavailable.
Any good suggestions?
/kews
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
