Yeah i think we can depricate IComponentBorder in 1.4 and point to IBehavior before/after and then remove it in 1.5 and maybe remote also **
public *final* Component setComponentBorder(*final* IComponentBorder border) in component or make it * public * *final* Component setComponentBorder(*final* IBehavior border) to make it more clear to people that a border can be set by using a behavior (else who knows..) On Sat, May 16, 2009 at 12:21, Juergen Donnerstag < [email protected]> wrote: > Hi, > > question: looking at that code > > // Call implementation to render component > final IComponentBorder border = > getComponentBorder(); > if (border != null) > { > border.renderBefore(this); > } > notifyBehaviorsComponentBeforeRender(); > onRender(markupStream); > notifyBehaviorsComponentRendered(); > if (border != null) > { > border.renderAfter(this); > } > > IComponentBorder could be implemented via a behavior as well. Is there > any reason why IComponentBorder needs this special treatment and why > it is not implemented as a behavior? > > -Juergen >
