in wicket the enabled status is controlled by the entire hierarchy. in order for a component to be enabled so must be all of its parents, all the way to the page. there are many reasons to do it this way and we will not change it. i suggest you either move the link out or disable on a more granular basis.
-igor On Mon, Sep 27, 2010 at 5:37 AM, Ludodo <[email protected]> wrote: > > Yes I did and it didn't works either. > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/setEnabled-true-doesn-t-enable-a-subcomponent-tp2715172p2715340.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > 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]
