|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object org.apache.wicket.markup.renderStrategy.AbstractHeaderRenderStrategy org.apache.wicket.markup.renderStrategy.ParentFirstHeaderRenderStrategy
public class ParentFirstHeaderRenderStrategy
This has been Wicket's default header render strategy before WICKET 1.5 which uses
MarkupContainer.visitChildren(org.apache.wicket.util.visit.IVisitor)
to traverse the hierarchy to
render the children headers.
Since child contributions are added to the markup after the parent contributions, children may
replace / modify existing settings. Which is not good. Instead the parent (container) should be
in control (see WICKET-2693).
Constructor Summary | |
---|---|
ParentFirstHeaderRenderStrategy()
Construct. |
Method Summary | |
---|---|
protected void |
renderChildHeaders(HtmlHeaderContainer headerContainer,
Component rootComponent)
Render the child hierarchy headers. |
Methods inherited from class org.apache.wicket.markup.renderStrategy.AbstractHeaderRenderStrategy |
---|
get, renderApplicationLevelHeaders, renderHeader, renderRootComponent |
Methods inherited from class java.lang.Object |
---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Constructor Detail |
---|
public ParentFirstHeaderRenderStrategy()
Method Detail |
---|
protected void renderChildHeaders(HtmlHeaderContainer headerContainer, Component rootComponent)
AbstractHeaderRenderStrategy
renderChildHeaders
in class AbstractHeaderRenderStrategy
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |