Also see:

pageNotFoundLogger

Also see:

PAGE_NOT_FOUND_LOG_CATEGORY

 public AnnotationMethodHandlerAdapter() 
{
	  
		// no restriction of HTTP methods by default
		super(false);
}

 protected ServletRequestDataBinder createBinder(HttpServletRequest request,
    Object target,
    String objectName) throws Exception 
{
		return new ServletRequestDataBinder(target, objectName);
}

Template method for creating a new ServletRequestDataBinder instance.

The default implementation creates a standard ServletRequestDataBinder. This can be overridden for custom ServletRequestDataBinder subclasses.

 public long getLastModified(HttpServletRequest request,
    Object handler) 
{
		return -1;
}

 public ModelAndView handle(HttpServletRequest request,
    HttpServletResponse response,
    Object handler) throws Exception 
{
		if (handler.getClass().getAnnotation(SessionAttributes.class) != null) {
			// Always prevent caching in case of session attribute management.
			checkAndPrepare(request, response, 0, true);
			// Prepare cached set of session attributes names.
		}
		else {
			// Uses configured default cacheSeconds setting.
			checkAndPrepare(request, response, true);
		}
		// Execute invokeHandlerMethod in synchronized block if required.
		if (this.synchronizeOnSession) {
			HttpSession session = request.getSession(false);
			if (session != null) {
				Object mutex = WebUtils.getSessionMutex(session);
				synchronized (mutex) {
					return invokeHandlerMethod(request, response, handler);
				}
			}
		}
		return invokeHandlerMethod(request, response, handler);
}

 protected ModelAndView handleNoSuchRequestHandlingMethod(NoSuchRequestHandlingMethodException ex,
    HttpServletRequest request,
    HttpServletResponse response) throws Exception 
{
		pageNotFoundLogger.warn(ex.getMessage());
		response.sendError(HttpServletResponse.SC_NOT_FOUND);
		return null;
}

Handle the case where no request handler method was found.

The default implementation logs a warning and sends an HTTP 404 error. Alternatively, a fallback view could be chosen, or the NoSuchRequestHandlingMethodException could be rethrown as-is.

 protected ModelAndView invokeHandlerMethod(HttpServletRequest request,
    HttpServletResponse response,
    Object handler) throws Exception 
{
		try {
			ServletHandlerMethodResolver methodResolver = getMethodResolver(handler);
			Method handlerMethod = methodResolver.resolveHandlerMethod(request);
			ServletHandlerMethodInvoker methodInvoker = new ServletHandlerMethodInvoker(methodResolver);
			ServletWebRequest webRequest = new ServletWebRequest(request, response);
			ExtendedModelMap implicitModel = new ExtendedModelMap();
			Object result = methodInvoker.invokeHandlerMethod(handlerMethod, handler, webRequest, implicitModel);
			ModelAndView mav =
					methodInvoker.getModelAndView(handlerMethod, handler.getClass(), result, implicitModel, webRequest);
			methodInvoker.updateModelAttributes(
					handler, (mav != null ? mav.getModel() : null), implicitModel, webRequest);
			return mav;
		}
		catch (NoSuchRequestHandlingMethodException ex) {
			return handleNoSuchRequestHandlingMethod(ex, request, response);
		}
}

 public  void setAlwaysUseFullPath(boolean alwaysUseFullPath) 
{
		this.urlPathHelper.setAlwaysUseFullPath(alwaysUseFullPath);
}

Set if URL lookup should always use the full path within the current servlet context. Else, the path within the current servlet mapping is used if applicable (that is, in the case of a ".../*" servlet mapping in web.xml).

Default is "false".

 public  void setCustomArgumentResolver(WebArgumentResolver argumentResolver) 
{
		this.customArgumentResolvers = new WebArgumentResolver[] {argumentResolver};
}

Set a custom ArgumentResolvers to use for special method parameter types. Such a custom ArgumentResolver will kick in first, having a chance to resolve an argument value before the standard argument handling kicks in.

 public  void setCustomArgumentResolvers(WebArgumentResolver[] argumentResolvers) 
{
		this.customArgumentResolvers = argumentResolvers;
}

Set one or more custom ArgumentResolvers to use for special method parameter types. Any such custom ArgumentResolver will kick in first, having a chance to resolve an argument value before the standard argument handling kicks in.

 public  void setMethodNameResolver(MethodNameResolver methodNameResolver) 
{
		this.methodNameResolver = methodNameResolver;
}

Set the MethodNameResolver to use for resolving default handler methods (carrying an empty @RequestMapping annotation).

Will only kick in when the handler method cannot be resolved uniquely through the annotation metadata already.

 public  void setParameterNameDiscoverer(ParameterNameDiscoverer parameterNameDiscoverer) 
{
		this.parameterNameDiscoverer = parameterNameDiscoverer;
}

Set the ParameterNameDiscoverer to use for resolving method parameter names if needed (e.g. for default attribute names).

Default is a org.springframework.core.LocalVariableTableParameterNameDiscoverer .

 public  void setPathMatcher(PathMatcher pathMatcher) 
{
		Assert.notNull(pathMatcher, "PathMatcher must not be null");
		this.pathMatcher = pathMatcher;
}

Set the PathMatcher implementation to use for matching URL paths against registered URL patterns. Default is AntPathMatcher.

 public  void setSessionAttributeStore(SessionAttributeStore sessionAttributeStore) 
{
		Assert.notNull(sessionAttributeStore, "SessionAttributeStore must not be null");
		this.sessionAttributeStore = sessionAttributeStore;
}

Specify the strategy to store session attributes with.

Default is org.springframework.web.bind.support.DefaultSessionAttributeStore , storing session attributes in the HttpSession, using the same attribute name as in the model.

 public  void setSynchronizeOnSession(boolean synchronizeOnSession) 
{
		this.synchronizeOnSession = synchronizeOnSession;
}

Set if controller execution should be synchronized on the session, to serialize parallel invocations from the same client.

More specifically, the execution of each handler method will get synchronized if this flag is "true". The best available session mutex will be used for the synchronization; ideally, this will be a mutex exposed by HttpSessionMutexListener.

The session mutex is guaranteed to be the same object during the entire lifetime of the session, available under the key defined by the SESSION_MUTEX_ATTRIBUTE constant. It serves as a safe reference to synchronize on for locking on the current session.

In many cases, the HttpSession reference itself is a safe mutex as well, since it will always be the same object reference for the same active logical session. However, this is not guaranteed across different servlet containers; the only 100% safe way is a session mutex.

 public  void setUrlDecode(boolean urlDecode) 
{
		this.urlPathHelper.setUrlDecode(urlDecode);
}

Set if context path and request URI should be URL-decoded. Both are returned undecoded by the Servlet API, in contrast to the servlet path.

Uses either the request encoding or the default encoding according to the Servlet spec (ISO-8859-1).

 public  void setUrlPathHelper(UrlPathHelper urlPathHelper) 
{
		Assert.notNull(urlPathHelper, "UrlPathHelper must not be null");
		this.urlPathHelper = urlPathHelper;
}

Set the UrlPathHelper to use for resolution of lookup paths.

Use this to override the default UrlPathHelper with a custom subclass, or to share common UrlPathHelper settings across multiple HandlerMappings and HandlerAdapters.

 public  void setWebBindingInitializer(WebBindingInitializer webBindingInitializer) 
{
		this.webBindingInitializer = webBindingInitializer;
}

Specify a WebBindingInitializer which will apply pre-configured configuration to every DataBinder that this controller uses.

 public boolean supports(Object handler) 
{
		return getMethodResolver(handler).hasHandlerMethods();
}