org.apache.wicket.markup.resolver
Class FragmentResolver
java.lang.Object
org.apache.wicket.markup.resolver.FragmentResolver
- All Implemented Interfaces:
- Serializable, IComponentResolver, IClusterable
public class FragmentResolver
- extends Object
- implements IComponentResolver
Usually you either have a markup file or a xml tag with wicket:id="myComponent" to associate
markup with a component. However in some rare cases, especially when working with small panels it
is a bit awkward to maintain tiny pieces of markup in plenty of panel markup files. Use cases are
for example list views where list items are different depending on a state.
Inline panels provide a means to maintain the panels tiny piece of markup in the parents markup
file. During the render process, when Wicket iterates over the markup file, the markup fragment
must be ignored. It is only indirectly referenced by component.
- Author:
- Juergen Donnerstag
- See Also:
- Serialized Form
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
FRAGMENT
public static final String FRAGMENT
- See Also:
- Constant Field Values
FragmentResolver
public FragmentResolver()
resolve
public Component resolve(MarkupContainer container,
MarkupStream markupStream,
ComponentTag tag)
- Description copied from interface:
IComponentResolver
- Try to resolve a component.
- Specified by:
resolve
in interface IComponentResolver
- Parameters:
container
- The container parsing its markupmarkupStream
- The current markupStreamtag
- The current component tag while parsing the markup
- Returns:
- component or
null
if not found
Copyright © 2006–2013 Apache Software Foundation. All rights reserved.