I don't like the idea of exposing Spring beans as attributes to JSP/JSTL because it violates the design principle that communication between controllers and views should pass through the model object. Accessing directly Spring beans in EL expressions couples the presentation tier to the other tiers in a far less than obvious way.
I even more dislike the idea of setting the default value of JstlView.exposeContextBeansAsAttributes to true as this encourage this bad practice (see
Furthermore this introduces a breaking change in the frequent case when a model attribute has the same name as a Spring bean. For instance in my applications many views and the corresponding command object share the very same name: up to 2.1M4 in the jstl page I used to get the model object, while in 2.5RC1 I get the view!
Thanks in advance for reconsidering this decision.