- All Known Implementing Classes:
public interface IRequestMapperMaps
Requests the implementation doesn't recognize, the
mapRequest(Request)methods must return
null. The workflow is: the Application class collects a set of
IRequestMappers and for each request the
request cycleasks these mappers whether any of them knows how to handle the current
url. Wicket pre-configures several mappers which are used for the basic application functionality like a mapper for the home page, a mapper for Wicket resources, for bookmarkable pages, etc. The user application can add additional mappers with the various WebApplication#mountXYZ() methods. The mapper has two main tasks:
- To create
IRequestHandlerthat will produce the response. When a request comes Wicket uses
getCompatibilityScore(Request)to decide which mapper should be asked first to process the request. If two mappers have the same score then the one added later is asked first. This way user’s mappers have precedence than the system ones. If a mapper knows how to handle the request’s url then it should return non-
The second task is to produce
IRequestHandler. This is needed at markup rendering time to create the urls for links, forms' action attribute, etc.
- Matej Knopp
All Methods Instance Methods Abstract Methods Modifier and Type Method Description
getCompatibilityScore(Request request)Returns the score representing how compatible this request mapper is to processing the given request.
IRequestHandler mapRequest(Request request)
request- provides access to request data (i.e. Url and Parameters)
- RequestHandler instance or
int getCompatibilityScore(Request request)Returns the score representing how compatible this request mapper is to processing the given request. When a request comes in all mappers are scored and are tried in order from highest score to lowest.
A good criteria for calculating the score is the number of matched url segments. For example when there are two mappers for a mounted page, one mapped to
/foo/barand the incoming request URL is /foo/bar/baz, the mapping to
/foo/barshould probably handle the request first as it has matching segments count of 2 while the first one has only matching segments count of 1.
Note that the method can return value greater then zero even if the mapper does not recognize the request.
- the compatibility score, e.g. count of matching segments