This class can be implemented by application developers, although this is not necessary, as {@link org.springframework.web.portlet.handler.PortletModeHandlerMapping}, {@link org.springframework.web.portlet.handler.ParameterHandlerMapping} and{@link org.springframework.web.portlet.handler.PortletModeParameterHandlerMapping}are included in the framework. The first is the default if no HandlerMapping bean is registered in the portlet application context.
HandlerMapping implementations can support mapped interceptors but do not have to. A handler will always be wrapped in a {@link HandlerExecutionChain}instance, optionally accompanied by some {@link HandlerInterceptor} instances.The DispatcherPortlet will first call each HandlerInterceptor's preHandle
method in the given order, finally invoking the handler itself if all preHandle
methods have returned true
.
The ability to parameterize this mapping is a powerful and unusual capability of this Portlet MVC framework. For example, it is possible to write a custom mapping based on session state, cookie state or many other variables. No other MVC framework seems to be equally flexible.
Note: Implementations can implement the {@link org.springframework.core.Ordered}interface to be able to specify a sorting order and thus a priority for getting applied by DispatcherPortlet. Non-Ordered instances get treated as lowest priority. @author John A. Lewis @author Juergen Hoeller @see org.springframework.core.Ordered @see org.springframework.web.portlet.handler.AbstractHandlerMapping @see org.springframework.web.portlet.handler.PortletModeHandlerMapping @see org.springframework.web.portlet.handler.ParameterHandlerMapping @see org.springframework.web.portlet.handler.PortletModeParameterHandlerMapping
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|