|
From: Darren D. <da...@da...> - 2004-07-29 13:42:21
|
> 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 y= ou > think that your use case is actually recommendable ;-) don't know whether it's recommendable or not, but it won't hurt to have i= t in if the default is to throw the exception I think. I'll modify local sources here and test (I'm at work and can't get to the CVS servers) and commit it tonight if there's no objections. > BTW, strictly speaking, we're still 100% compatible to Spring 1.0, beca= use > the "exposeSessionAttribute" feature has been introduced in Spring 1.0.= 2 > ;-) oooh - slippery, but I'm not letting you get away with it that easily.. <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> hehe ;-) Cheers! --=20 Darren Davison Public Key: http://www.davison.uk.net/pages/key.htm |