RE: [Springframework-developer] About MVC

[<dar...@hs...>]

<Alef>
Darren, I've been implementing something like this before, using the
reference data feature of the controllers, works like a charme. However,
It's the problem still is that you end up using _one_ model, where - in
e.g. a portlet - you would somehow want a per-portlet model, scoped,
like in tiles... In your solution, what if one of the beans returns an
entry in the model with the same key as the controller (or another
bean). They override...
</Alef>


yeah, that's actually the way I understood the OP's request - as being a
non-portal scenario, and in some (non-portal) apps it's definitely what
you'd want I think.  For portlets, you would of course need properly scoped
models but I think what was outlined has some validity.

<Alef>
It would however be nice if we could come up with something that's not
specific to views...
</Alef>

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)

Darren.




_____________________________________________________

This transmission has been issued by a member of the HSBC Group 
"HSBC" for the information of the addressee only and should not be 
reproduced and / or distributed to any other person. Each page attached 
hereto must be read in conjunction with any disclaimer which forms part 
of it. Unless otherwise stated, this transmission is neither an offer nor the 
solicitation of an offer to sell or purchase any investment. Its contents are 
based on information obtained from sources believed to be reliable but
HSBC makes no representation and accepts no responsibility or liability as 
to its completeness or accuracy.