- All Implemented Interfaces:
- Serializable, IClusterable, IComponentResolver
public class BorderBodyResolver
- extends Object
- implements IComponentResolver
In case of Border where the associated markup has a container in between the wicket:border and
the wicket:body tag, the wicket:body container can not be resolved easily. Lets assume the
container in the middle is a Form container, than this Form container does not know how to
resolve the wicket:body. Only the Border component does know how to do it.
Until 1.3, the original Border implementation, resolved these markup vs component hierarchy
mismatches, but the new implementation by purpose no longer does. We want to minimize such
mismatches for simplicity and clarity reasons. No magic.
NOTE: This resolver will be removed again in Wicket 1.4(!)
- Juergen Donnerstag
- See Also:
- Serialized Form
|Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
public boolean resolve(MarkupContainer container,
- Description copied from interface:
- Try to resolve the tag, then create a component, add it to the container and render it.
- Specified by:
resolve in interface
container - The container parsing its markup
markupStream - The current markupStream
tag - The current component tag while parsing the markup
- true, if componentId was handle by the resolver. False, otherwise
- See Also:
Copyright © 2004-2011 Apache Software Foundation. All Rights Reserved.