The problem with doing things this way is that a user will still have access to parts of your system unless you're locking down URLs based on role as well. Just because the URL isn't there doesn't mean they can't get to it.
While this may be useful for your project, I don't think it's useful for the general AppFuse audience. If other users start to see this thread and/or the JIRA issue created and there's more demand for it, we may add it then. Matt On Sun, Sep 20, 2009 at 3:30 AM, measwel <marek_karczew...@yahoo.com.au>wrote: > > Well, I want to discern different types of users. Based on the type, I want > the system to expose different functionality. Roles seemed quite useful for > this, as I can both set the type by assigning a role to the user and render > a menu dynamically. > > I found out that when a menu is specified for a role which the user does > not > have, it is not rendered. > -- > View this message in context: > http://www.nabble.com/dynamic-menu-rendering-based-on-user-roles-tp25513990s2369p25528883.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net > For additional commands, e-mail: users-h...@appfuse.dev.java.net > >
