I'm doing some component-based authorization and I'm trying to disable an entire RadioGroup without having to tie the authorization to each individual Radio button. Were I to directly disable the RadioGroup, it looks like the Radio buttons would also disable (but I haven't tested this); but it will not disable all the choices when I tie an authorization strategy to the RadioGroup.
I'm working with wicket 1.3.3, so has this problem been addressed in a later versoin, and if not, is there some reason we might not want to do this? Thanks. Joel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
