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

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

Well spotted, Darren - I added those checks because I considered it an =
error to silently override existing attributes. Unfortunately, you had a =
use case for just that... We can certainly make this configurable, if =
you think that your use case is actually recommendable ;-)

BTW, strictly speaking, we're still 100% compatible to Spring 1.0, =
because the "exposeSessionAttribute" feature has been introduced in =
Spring 1.0.2 ;-)

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Darren Davison
Sent: Thursday, July 29, 2004 12:51 PM
To: spr...@li...
Subject: Re: [Springframework-developer] Velocity / FreeMarker request
and session attributes



> 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 :-)

actually, is there any value in adding (yet) another bean property to
AbstractTemplateView that defines the behaviour here?

myVelocityView.allowSessionOverride=3Dtrue

to force the old behaviour, with the default being false which causes =
the
ServletException to be thrown?  Otherwise, I have to start kludging =
model
attribute names somehow I think..

Regards,

--=20
Darren Davison
Public Key: http://www.davison.uk.net/pages/key.htm




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer