Subject: Re: controllers calling controllers in MVC? From: Vic C <[EMAIL PROTECTED]> === If possible you should have a controller call a controller. A good parctice is to have a page controler for each page. It then decied whom to forward to. The part of a good pracitice is that the page controller should allwyas only call it's own JSP and if it need to go to another JSP, it calls its controller. When a page needs to leve the current page, it would also go to it's own controller to clean up and forward.
I am guessing, but maybe you also want to use a Struts menu from SourceForge.com. Vic Richard Diaz wrote: > Controller Servlets of course using MVC (servlets and > JSP) > > Does anyone do this? > > Any side effects? > > Should it be avoided? > > Here is the issue: > > I have: > ControllerServlet_1 > ControllerServlet_2 > ControllerServlet_3 > ControllerServlet_4 > > sometimes I need to call 1 and 3 > > othertimes I just need 2 and 3 and 4 > > another time i need 4 and 2 in that order. > > should I use JSP for the calling of these OR make > -super-controller servlets that call the controller > servlets i need. > > thanks for any insight, > Rich > > __________________________________________________ > Do You Yahoo!? > LAUNCH - Your Yahoo! Music Experience > http://launch.yahoo.com > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
