why not just introduce that interface and the impl in component? So why also alter abstract behavior? Because that would mean that suddenly almost all the behaviors that are used are suddenly also IComponentConfigurationBehavior And 99.9% of them don't do anything.
On Sat, Feb 19, 2011 at 04:17, Jeremy Thomerson <jer...@wickettraining.com> wrote: > What does everyone think about the following patch [1] to add two methods to > IBehavior? Obviously, it's not added directly to IBehavior since that would > be a breaking API change. It's added to a sub-interface that can optionally > be implemented by IBehaviors and is implemented by AbstractBehavior by > default. > > It's for the purpose of allowing behaviors to contribute to things like the > visibility and enabled status of a component, which they can't currently do > in beforeRender because that happens during the render cycle, at which time > such changes are not allowed. > > [1] - http://mysticpaste.com/view/8231 > > -- > Jeremy Thomerson > http://wickettraining.com > *Need a CMS for Wicket? Use Brix! http://brixcms.org* >
