|
From: Darren D. <da...@da...> - 2004-08-04 09:20:40
|
> So there's actually 2 scenarios, with 2 options each: > > 1. > a) let session attributes override model attributes > b) throw an exception if session attributes would override model attrib= utes > > 2. > a) let model attributes override session attributes > b) throw an exception if model attributes would override session attrib= utes > > And then there's the same for request attributes... I guess it's better= to > keep stuff simple here, i.e. assume typical use cases rather than allow= for > all those configuration options. I've just changed AbstractTemplateView to expose 2 new bean properties; allowSessionOverride and allowRequestOverride both with default : false. Current behaviour is maintained - ServletException thrown if a request or session attribute would hide a model attribute - unless one of these prop= s is explicitly set to allow it. I think this is the clearest way. It's the simplest option - it's likely I'm the only user who needs this j= ust now anyway so anything further would be a case of YAGNI. Regards, --=20 Darren Davison Public Key: http://www.davison.uk.net/pages/key.htm |