Thanks a lot. Your comments are very helpful. I believe with view data you mean that is kind of static data not tied to business logic. For example menus soemtime are dependent on Roles and/or business rules. In that case menus should also be loaded from controller. Is it correct?
On Thu, Oct 29, 2009 at 4:28 PM, Antonio Petrelli < [email protected]> wrote: > 2009/10/29 anyz <[email protected]>: > > When using with Spring 2.5, What is best way to prepare data for Tiles. > > > > 1- Prepare data in Spring controller or set the delegator property with > > methodNameResolver for controller and put data fetch logic in it. > > > > 2- After some validation etc controler can throw ModeView to render > tiles. > > Tiles preparer class can then fetch required data for it from DB. > > > > What can be pros and cons of two apparoaches or any other better > alternate. > > > This question can be generalized to non Spring applications too: is it > better to load data from C part of an MVC application, or from the > preparer? > > Using a preparer you have a modular dependency between data used in a > portion of the page and the portion itself. However, using a > controller you have a centralized point where you load all the > necessary data to render the page correctly. > IMHO a mixed approach is better: > > If it is business data, then it is better to load it from the controller. > If it is view data (for example a menu, a list of link etc.) then > probably it is better to load it in a preparer. > > Antonio >
