wicket.markup.resolver |
wicket.markup.resolver package
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.
|
Java Source File Name | Type | Comment |
AutoComponentResolver.java | Class | <wicket:component class="myApp.MyTable" key=value> tags may be used to add
Wicket components (e.g. |
AutoLinkResolver.java | Class | The AutoLinkResolver is responsible to handle automatic link resolution. |
FragmentResolver.java | Class | Usually you either have a markup file or a xml tag with
wicket:id="myComponent" to associate markup with a component. |
HtmlHeaderResolver.java | Class | This is a tag resolver which handles <head> and
<wicket:head>tags. |
IComponentResolver.java | Interface | ApplicationSettings maintains a list of IComponentResolvers. |
MarkupInheritanceResolver.java | Class | Detect <wicket:extend> and <wicket:child> tags,
which are silently ignored, because they have already been processed. |
ParentResolver.java | Class | Some containers are transparent to the user (e.g. |
ScopedComponentResolver.java | Class | 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, effectivly
providing something like scoping for wicket id resolution.
Note: This resolver is not activated by default. |
WicketLinkResolver.java | Class | This is a tag resolver which handles <wicket:link> tags. |
WicketMessageResolver.java | Class | This is a tag resolver which handles <wicket:message
attr="myKey">Default Text</wicket:message>. |