On 8/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > First off, thanks for all the work on struts-menu... it's quite useful! > > I was working with VelocityMenuDisplayer and noticed that the permissions > checks were "all or nothing" per menu. It checks the top level menu > definition, in "void display(MenuComponent menu)", but doesn't go through > and evaluate permissions/roles on specific Items. > > I wrote a child class of VelocityMenuDisplayer that would do fine-grained > item based permission checking, and remove Items that the user should not > see. Is this something you'd be interested in taking a look at? It appears > to work for my purposes and I'm more than happy to share..
We previously had such a feature, but the problem was we were removing items for all users, not just the current user - so the removal of items was "sticky" in a sense. http://issues.appfuse.org/browse/SM-58 To solve that, we've recently moved all the permission checking into the templates themselves. Matt > > (Either that or I messed something up!) > > Thanks :) > > John > > -- http://raibledesigns.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ struts-menu-devel mailing list struts-menu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/struts-menu-devel
