phponlinetutorial

model 2 architecture in struts  controlling  logic is completely secerated  from presentation logic  .   model 2 architecture controller part can be implemented  using servlet model 2 architecture view  part can be implemented  using  jsp model 2 architecture model  part can be implemented  using ejb3 or spring  in the model 2 architecture servlet is providing single entry point to all of the client .

Struts 1.x vs Struts 2.x Main Differences  In struts 1  front controller is ActionServlet         In 2.x front controller is FilterDispatcher     In struts 1.x we have RequestProcessor class         In 2.x we have Interceptors instead RequestProcessor will see about this concept later just remember as of now     In struts 1.x we have multiple tag libraries like, html, logic, bean..etc         In 2.x we do not have multiple libraries, instead we have single library which includes all tags     In struts 1.x the configuration fine name can be [any name].xml and we used to place in web-inf folder         In 2.x the configuration file must be struts.xml only and this must be in classes folder     In struts 1.x we have form beans and Action classes separately     ...

        delegates the  request to right business apps   performs required persistence operation  (curd operation )  collects response content form the corresponding business apps    the above architecture describe us to design  single jsp page responsible for accepting client request ,forwarding it to the right business app collecting response content  form the corresponding business app preparing and desplaying the presentaion on the browser  the  above architecture is simple but the problem is presentation logic and controlling logic  combining  implemented inside  one single page  i.e, we don't have any proper separation in b/w   controlling logic and presentation logic  to remove the above  described  problem  sum introduced one more architecture with a name model-2   

 mvc is one architecture  pattern describes as to devide our system in to 3 parts   model : responsible for business logic  view :  responsible for presentation logic controller : responsible for controlling logic                  what is  controlling logic ? controlling logic is nothing but controlling request &response flow i.e, Accepting the  client request , delegating the request to model, collecting the response from model ,making available the response content to view and dispatching the control to view . why to follow MVC?         for the purpose of " loose -coupling and parallel development"   in java also we are having  some recommended architectures  using which we can make our apps design as simple possible model -1 architectures   

 Frame work is one reusable semi-finished app witch provides some  common services  to our app and  that can be customized according to our requirement  

  struts is one web MVC based  framework  from " Apache s/w foundation "   using which we can design industry oriented mvc based web apps