On 11.01.12 20:42, Will Cheung wrote: > I think the problem could not be solved yet because userB's TorqueUser > instance is session record, which is cached and should not > synchronized automatically even if userA modifys his record in > database. > > Am I right?
Yes you are. And then you have the sessionUnbind issue as pointed out by Sheldon. But still there is help. You may use the SessionService (you'll need to add the SessionListener to your application) to get access to your active sessions like in TurbineSession.getSessionsForUser(user) and then update the user object in those sessions. However I'm still not sure about the use case. Are you absolutely sure that you want to modify user settings of other users? Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
