Hello, I have an idea and I have a sneaky suppision that it's wrong so I'm going to post it here and see if there's anything wrong with it.
On the front-end I have several display components that are used over and over again on several pages of my app. Individually, each of these display components require their own unique data to be loaded into the Request, Response or ModelAndView . That being said, assuming that more than one of the page share the same display component: Is it okay to, have a Collection of "display component controllers" which populate the Request, Response, and ModelAndView with the data needed for each component inside of a parent Controller? (set by the IoC container of course) To me what I mentioned above sounds like a portlet system. But it also seems to me that maybe SpringMVC might be flexible enough that you could just chain up a couple of Controllers together to do the same thing before displaying the view (that's why I have a suppision that what I am proposing might be wrong). Could someone please offer me some insight on this? (If what I wrote doesn't make any sense, please let me know, I've tried to be as clear as possible...) Thank you, Andrew J. Leer -- View this message in context: http://www.nabble.com/Question-on-SpringMVC-Controllers-tf2940262s2369.html#a8220992 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
