On Jun 20, 2012, at 10:12 AM, Jacques Le Roux wrote: > I slept on it and here is what I will do. > > When using DeltaManager, I remember crossing issues with session > serialisation at logout (due to Java Objects in session and, as I said, also > dispatcher, security and authz object, though I don't clearly remember for > the last 3). > Now that I think about it, what I wrote there was an ugly workaround that I > should never have committed as is. > > What I propose: > revert your change Jacopo > revert my initial commit and related backports > > Because I want to be able sometimes to use DeltaManager with only its > distributable capabilities not session persistence (which comes with some > troubles) > I want to introduce later the same workaround but not as I did. I'd want to > use a sessionPersistence bollean properties rather, to make things totally > independent from the Manager > Anyway it will be only when I will get enough time to properly investigate > this again...
Ok, for a change like this I would like to review your solution before it is committed, so when you will implement the changes that you would like to contribute, please share the patch for community review. Thanks, Jacopo > > Jacques > > From: "Jacopo Cappellato" <jacopo.cappell...@hotwaxmedia.com> >> On Jun 19, 2012, at 10:46 PM, Jacques Le Roux wrote: >> >>> Mmm, we could also remove the whole initial commit and all backports. >> >> This would be ideal... the whole commit seems to add unwanted complexity >> just to handle a specific use case that could probably be managed with >> different approaches,if properly discussed/designed with the community. >> >>> Simply all objects put in session would need then to be serialized... >> >> This was the first thing I thought when I discovered the bug and your commit >> while I was debugging the error yesterday. >> >> Kind regards, >> >> Jacopo >>
