Package org.apache.wicket.markup.resolver

Resolvers implement the IComponentResolver interface and must be registered with the application.

See:
          Description

Interface Summary
AutoLinkResolver.IAutolinkResolverDelegate Interface to delegate the actual resolving of auto components to.
IComponentResolver ApplicationSettings maintains a list of IComponentResolvers.
 

Class Summary
AutoComponentResolver <wicket:component class="myApp.MyTable" key=value> tags may be used to add Wicket components (e.g.
AutoLinkResolver The AutoLinkResolver is responsible to handle automatic link resolution.
AutoLinkResolver.AbstractAutolinkResolverDelegate Abstract implementation that has a helper method for creating a resource reference.
AutoLinkResolver.AutolinkBookmarkablePageLink<T> Autolink components delegate component resolution to their parent components.
AutoLinkResolver.PathInfo Encapsulates different aspects of a path.
BorderBodyResolver 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.
ComponentResolvers Utility class for IComponentResolvers
EnclosureResolver This is a tag resolver which automatically adds a Enclosure container for each <wicket:enclosure> tag.
FragmentResolver Usually you either have a markup file or a xml tag with wicket:id="myComponent" to associate markup with a component.
HtmlHeaderResolver This is a tag resolver which handles <head> and <wicket:head>tags.
MarkupInheritanceResolver Detect <wicket:extend> and <wicket:child> tags, which are silently ignored, because they have already been processed.
ParentResolver Some containers are transparent to the user (e.g.
ScopedComponentResolver Implement a component resolver which walks up the component tree until a Page or Panel and tries to find a component with a matching wicket id, effectively providing something like scoping for wicket id resolution.
WicketContainerResolver This is a tag resolver which handles <wicket:container> Sometimes adding components in certain ways may lead to output of invalid markup.
WicketLinkResolver This is a tag resolver which handles <wicket:link> tags.
WicketMessageResolver This is a tag resolver which handles <wicket:message key="myKey">Default Text</wicket:message>.
 

Package org.apache.wicket.markup.resolver Description

Resolvers implement the IComponentResolver interface and must be registered with the application. Most of them are registered by default. Resolvers are used by Wicket to find the Component associated with markup (wicket:id) where the Component is not simply a child of the parent container.



Copyright © 2004-2011 Apache Software Foundation. All Rights Reserved.