Mailing-List: contact click-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: click-dev@incubator.apache.org
Message-ID: <865049886.1239826635257.JavaMail.jira@brutus>
Date: Wed, 15 Apr 2009 13:17:15 -0700 (PDT)
From: "Bob Schellink (JIRA)" <jira@apache.org>
To: click-dev@incubator.apache.org
Subject: [jira] Commented: (CLK-406) Menu improvements - plug-able role
 checking.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLK-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699352#action_12699352 ] 

Bob Schellink commented on CLK-406:
-----------------------------------

@Joseph, can you expand on the onSecurityCheck usage? First, how is this suppose to work and second what are the advantages?

> Menu improvements - plug-able role checking.
> --------------------------------------------
>
>                 Key: CLK-406
>                 URL: https://issues.apache.org/jira/browse/CLK-406
>             Project: Click
>          Issue Type: Improvement
>          Components: extras
>            Reporter: Demetrios Kyriakis
>
> Please improve the Menu Control, by allowing the user to have a plug-able role cheking for the menu items.
> Right now the Menu Control is using HttpRequest#isUserInRole(String role), but most webapplications
> don't use this strategy for user/roles management, so this method returns false for all those cases :(.
> This is very limiting, making the existing Menu Control useless for most user applications, thus forcing the users
> to make their own menu controls (or the hack the original one). 
> Please allow to set a different method for this operation by the user (if no other is used, of course, the default one - mentioned above - would be used as before - so 100% backwards compatible).
> Thank you,
> Demetrios.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.