Or more quick and dirty, override isEnabled of the components you target and let it return true or false depending on the current user.
Eelco On 3/6/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > So you should set them only disabled according to specific user > attributes. See wicket.authorization.Action.ENABLE for something that > is useful in this context. > > Eelco > > On 3/6/07, tooy li(Gmail) <[EMAIL PROTECTED]> wrote: > > When i set the html element to readonly or disabled , the wicket form > > cannot get the value of these specficed field. and I have control these > > fields accord to the different user. > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share your > > opinions on IT & business topics through brief surveys-and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Wicket-user mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
