://www.nabble.com/hide-show-components---role-based-tf4550513.html#a12991489
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
MyPage() {
Link myLink = ...;
MetaDataRoleAuthorizationStrategy.authorize(myLink, RENDER,
role1,role2);
}
}
--
View this message in context:
http://www.nabble.com/hide-show-components---role-based-tf4550513.html#a12991489
Sent from the Wicket - User mailing list
On 10/2/07, Juan Gabriel Arias [EMAIL PROTECTED] wrote:
The second one.
Components should check some roles and enable or disable itself.
Just look closely at how wicket-auth is implemented. It is basically
an example project to show how you can do this stuff yourself.
Note that there is
for a description of how I do context (or data) sensitive
roles.
http://www.nabble.com/Best-Practices-for-accessing-repainting-sibling-cousin-components--tf3841514.html#a10895313
Chuck
--
View this message in context:
http://www.nabble.com/hide-show-components---role-based-tf4550513.html
Hi all,
im working with Wicket 1.2.4, Spring and Acegi.
Im trying to dinamically show or hide html components, like links, buttons,
etc.
Is there a best practice in wicket?
Im also using wicket-auth-roles, and i've been digging a little, but i
couldn't find a way to do this.
BTW, i already
this message in context:
http://www.nabble.com/hide-show-components---role-based-tf4550513.html#a12991489
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
