RE: [Springframework-developer] About MVC

[Alef A. \(JTeam\) <al...@jt...>]

> Do you not think that configuring some of this peripheral 
> data should be at the view level?  If not the view, then 
> where..? In common scenarios I come across, the secondary 
> model is quite specific to a view (though not of course the 
> TYPE of view)

From what I've seen there's three commons scenerio's

1. Reference data needed to render the view. This is the stuff we have
already.
2. Data related to the view but not necessarily needed to render it
(additional news in a sidebox, perhaps a menu).
3. Componentized views having corresponding controller (portlet)

The first case can perfectly be implemented using our current reference
data implementation (a list of elements in a select box of a form for
instance). One controller, having reference data, specifically belonging
to the controller

The second case (sideboxes containing news, a menu that needs
information not related to the main view) I consider to be a simple
Tiles approach and I think a somewhat more advanced version of the
reference data features we have now, would do. Something like you
proposed maybe. Reference data, however, not in fact related to the
controller!

The third case however, is a completely different one and somewhat looks
like the portlet approach. I think this is a bit too far-fetched to
implement in Spring, although I'd like to offer view-tech independent
stuff for this. Parallel controllers rendering views independent of
eachother.

It's just some rambling, but maybe we could brainstorm about this more
in order to come with something brilliant :)...

Alef