> I do understand that there are workarounds for this (and I'm > implementing one myself right now). The question is: would this be a > good idea for wicket itself or am I missing something here?
Nope, an isEnabledInHierarchy sound like a good idea to me. I'm just a little worried what this will do to performance. It's one thing to call isEanbled for every (visible?) component but It's a whole other order of magnitude to call isEnabledInHierarchy for every component which in turn calls isEnabledInHierarchy on every parent, etc etc. Especially because isEnabledInHierarchy will have to check isEnabled and isEnableAllowed on the component itself. With isEnabled being mostly a boolean return that is not the biggest problem but isEnableAllowed goes directly into the security framework which can do pretty much everything even db lookups or file reads if they want to. Caching these results for the duration of the request might be a solution but could also open up a whole other can of worms. Maurice
