Steps for struts work flow:
- web container loads web.xml and verifies whether the url-patterns are verified or not?, if matches web-container transfers the request to Filter Dispatcher
- Filter Dispatcher 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 Configuration Manager 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 Action Proxy.
- Action Proxy delegates the request along with its information to Action Invocation.
- Action Invocation 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.
- Action Invocation receives finally result produced by an Action class.
- Action Proxy transfers the result back to FilterDispatcher
- Filter Dispatcher selects an appropriated view, basing on the result
- Finally Filter Dispatcher uses Request Dispatchers forwarding mechanism and forward a view as a response back to the client.
No comments:
Post a Comment