well, there are plenty of uses of this in our code, have a look there -igor
On Wed, Apr 7, 2010 at 2:51 PM, Janani Sundarrajan <[email protected]> wrote: > Doesn't seem to work either! > > -----Original Message----- > From: Igor Vaynberg [mailto:[email protected]] > Sent: Wednesday, April 07, 2010 4:48 PM > To: [email protected] > Subject: Re: Wicket Authorization (Using MetaDataKey) > > public static MetaDataKey<RoleCheck> priv = new > MetaDataKey<RoleCheck>(){}; > > -igor > > On Wed, Apr 7, 2010 at 2:23 PM, Janani Sundarrajan > <[email protected]> wrote: >> Hello, >> >> I am trying to implement a simple authorization strategy for my Wicket >> application. I am implemented my own AuthorizationStrategy (extending >> IAuthorizationStrategy). >> >> http://old.nabble.com/Authorization-strategy-help-td18948597.html After >> reading the above link, I figured it makes more sense to use >> metadata-driven authorization than one using Annotations. >> >> So I have a simple RoleCheck class >> >> public class RoleCheck { >> >> private String privilege; >> >> public RoleCheck(String priv) { this.privilege = priv; } >> >> public void setPrivilege(String privilege) { this.privilege = privilege; > } >> >> public String getPrivilege() { return privilege; } >> >> } >> >> I add it a component public static MetaDataKey priv = new MetaDataKey() >> {}; editLink.setMetaData(priv, new RoleCheck("Update")); >> >> And in my Authorization Strategy class, I try to get the metadata >> associated with the component >> >> public boolean isActionAuthorized(Component component, Action action) { > if >> (action.equals(Component.RENDER)) { RoleCheck privCheck = (RoleCheck) >> component.getMetaData(EditControlToolBar.priv); if (privCheck != null) { >> ... } } >> >> However the getMetaData gives an error "Bound mismatch: The generic > method >> getMetaData(MetaDataKey) of type Component is not applicable for the >> arguments (MetaDataKey). The inferred type RoleCheck is not a valid >> substitute for the bounded parameter " >> >> Any help would be appreciated. Thank you >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
