|
From: Darren D. <da...@da...> - 2004-07-29 10:13:25
|
1.1RC1 looks to have implemented a change to the behaviour in 1.0.2 for exposing session or request attributes. Previously, they would silently be added to the model hiding model attributes of the same name. Now it throws a ServletException if a model attribute of the same name exists. This affects one of my projects which assumes session scoped objects are superior to controller generated values, so I now get an error page on requests that tickle this functionality. I think it's good to make the behaviour explicit and I'll change my controller code to manage the change, but just to be aware - it's not 100= % backward compatible with 1.0.2 as advertised :-) Cheers! --=20 Darren Davison Public Key: http://www.davison.uk.net/pages/key.htm |