Hi folks,
Timothy Bennett and I have been thinking about how to hook Guardian
(http://guardian.safehaus.org), a simple authorization API into Wicket
so we can *declaratively* control the visibility of components on
pages. More complex interactions though where you alert the user about
their lack of permissions where appropriate is another issue.
We specifically want to add a small piece of generic code which is not
application specific (like a plugin) to enable or disable components
based on permissions. For example we could use the id of a component as
the name/label of a permission so the generic code can enable or disable
the component. However interacting with the user is another concern as
I mentioned above. Is there some best practice for adding such
functionality?
Do you have any advice on how we might approach this endeavor?
BTW, yes, the recent discussions regarding security frameworks has
triggered this question :).
Thanks,
Alex
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
