Oh yeah. Front Controller is another J2EE pattern, and it just happens to be on the exam. Actually, Struts is a really fancy example of using a Front Controller pattern. The basic idea of the Front Controller pattern is that a single component, usually a servlet but possibly a JSP, acts as the single control point for the presentation tier of a web application. With the Front Controller pattern, all of the app’s requests go through a single controller, which handles dispatching the request to the appropriate places.
In the real world, it’s rare to implement a Front Controller all by itself. Even a really simple implementation usually includes another J2EE pattern called an Application Controller. Struts includes a class called the RequestProcessor, which is ultimately responsible for the handling of HTTP requests.
Although the exam might contain questions about the Front Controller pattern, you’ll be fine if you remember the benefits of Struts, and the fact that Struts is simply a Front Controller with all the bells and whistles.
Eight features that Struts adds to a Front Controller
1 Declarative Control: Struts allows you to create declarative maps between request URLs, validation objects, model-invoking objects, and views.
2 Automated Request Dispatching: The Action.execute() method returns a symbolic ActionForward which tells the ActionServlet which view to dispatch to. This provides another layer of abstraction (and loose coupling) between the controller ...