Struts-Execution process

• When a client request is given, a Web container would receive request
• Web container loads XML and verifies whether the url-patterns is verified or not, if matches Web-co Ntainer transfer the request to Filterdispatcher
• filterdispatcher hand overs the request to Actionproxy, it's a proxy class which is responsible to APPL Y before and after services to original business logic
• actionproxy Contacts Configuraionmanager class, to know the suitable Action for the request and the need Ed Services for the request
• ConfigurationManager class loads structs.xml and provides the required information back to ACTIONPR Oxy
• ACTIONPORXY delegates the request along with its information to Actioninvocation
• Actioninvocation executes the interceptors added to a Action from 1–n, after that it'll call the BU Siness logic implemented from n–1 in reverse order
• Actioninvocation receives finally result produced by an action AClass
• Actionproxy transfers the result back to Filterdispatcher
• Filterdispatcher selects an appropriate view, basing on the result
• Finally Filterdispatcher uses requestdispatchers forwarding mechanism and forward a view as a response back to th E-Client

Struts-Execution process