SpringMVC theory

Development around the Handler page View Data Model

SpringMVC of running processes:

  1, the user sends a request, the request is mapped to all the DispatcherServlet (central servlet controller, which intercepts all requests servlet)

  2, the default will be used DefaultAnnoationHandlerMapping, a major role mapping url, that correspond to the url handler.

  3, default DefaultAnnoationHandlerAdapter, used for handler adapter,

  4, the controller will eventually link up our own development, if the use of interceptors, the interceptor will be bound to process them

  5, when the final output modelAndView, delivered to the central controller.

  6, InternalResourceViewResolver (default jsp of view)

  7, the junction model, and list.jsp phase and return.

Http request address mapping principle

  1, the user sends a request to the tomcat or jetty container, SpringMVCHandlerMapping default when using annotations, this is a new version of the default configuration, annotated maps correspond to the way we will eventually achieve their own rear end.

Notes @RequestMapping mapping techniques:

  Supports standard url, Ant-style url (ie,?, *, **), a placeholder with parentheses url

Guess you like

Origin www.cnblogs.com/niuyg928/p/11494916.html