Well, i have implemented a different authorization model and don't use the annotation based. All restrictions are written in one onfig file to have them all in place. I there is a viewonly user I don't want to disable each panel/textfield ... one by one, so that’s why I disable the whole page.
-----Ursprüngliche Nachricht----- Von: Marat Radchenko [mailto:slonopotamusor...@gmail.com] Gesendet: Freitag, 15. Januar 2010 15:20 An: users@wicket.apache.org Betreff: Re: Disabled Navigation if Action.ENABLE is restricted for page Why you're disabling whole page in first place? 2010/1/15 Giambalvo, Christian <christian.giamba...@excelsisnet.com>: > Hi all, > > i have a litte problem. > > I have implemented an own AuthorizationStrategy where I check I a user > is allowed to render/enable a component/page. > Each page has a navigation. If I restrict enable for a page, then the > navigation gets also disabled. > I tried overwriting isEnabled() for the whole navigation and its childs, > but doesn't work. > So the main question is "how to have a component on a page always be > enabled even if the page is disabled"? > > Greets chris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
