Life Cycle of Struts with diagrams (figures)

pic2:

pic 3:

pic 4:

pic 5:

pic 6:

pic 7:

pic 8:

pic 9:

• web container loads web.xml and verifies whether the url patterns are verified or not? If matches web-container transfer the request to FilterDispatcher
• FileDispatcher handsover the request to ActionProxy, it is a proxy class which is responsible to apply before and after services to original business logic.
• Action proxy contacts ConfigurationManager class to know the suitable Action for the request and the needed services for the request.
• Configuration class loads struts.xml and provides the required information back to ActionProxy
• ActionProxy delegates the request along with its information to ActionInvocation
• ActionInvocation executes the interceptors added to an Action form 1-N requests, after that it will calls the business logic implemented from N-1 in reverse order
• ActionInvocation receives finally result produced by an Action class
• ActionProxy transfers the result back to FilterDispatcher
• FilterDispatcher selects an appropriate view, based on the result
• finally FilterDispatcher uses RequestDispatchers forwarding mechanism and forward a view as a response back to the client