There are many ways to create controllers and many things to consider when designing controllers to meet a variety of requirements. The one single purpose of a controller is to properly handle a request coming from a client—for example a web browser—typically as the result of a user’s action or interaction in a web page. There is a need to also understand how to configure controllers to support various requests from multiple web pages.
- [Instructor] Now that we've looked closer at how JEE…and Spring context impact application behavior,…let's turn our attention to the flow of request…through a series of Spring components…and it all begins with the dispatcher servlet.…I like to call the dispatcher servlet…the traffic cop of components…because it plays a major role in how requests get handled…and ultimately how responses make it back…to the user's web browser.…This is another set of component interactions…that's critical to understand deeply…so that you can make better design, development,…and troubleshooting decisions.…
The dispatcher servlet is out front…in the request processing workflow…and thereby governs a lot of the routing logic…for request processing.…It does so by delegating…to special purpose Spring managed beans…that each play a particularly useful role in the workflow.…Let's walk through them now.…First there's the handler map.…It maps a request to its appropriate handler.…A handler is typically a controller.…
The type of mapping comes in different varieties,…
Released
5/3/2018- Using Spring MVC for web projects
- Spring MVC controllers
- Creating controllers and views
- Spring MVC models
- Creating the model
- Request mapping
- Spring MVC views
- Custom app configuration
Share this video
Embed this video
Video: Request processing components