RE: [Springframework-developer] Velocity / FreeMarker request and session attributes

[<jue...@we...>]

> <PedanticQuoteFromRod'sTssPostAndFinalWordOnTheMatter>
> Spring 1.1 final is scheduled for release in mid August, and will be =
100%
> backward compatible with Spring 1.0.2.
> </PedanticQuoteFromRod'sTssPostAndFinalWordOnTheMatter>

Damn ;-)

Seriously, we can allow overriding by default, of course. Question is: =
Aren't there also valid uses cases for letting model attributes override =
session attributes, i.e. the other way round?

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 =
attributes

2.
a) let model attributes override session attributes
b) throw an exception if model attributes would override session =
attributes

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.

Juergen