@turbine.apache.org
> Subject: Re: TorqueUser synchronization problem
>
> On 12.01.12 16:11, Sheldon Ross wrote:
> > In order to get around this, we actually update TurbineSecurity (Turbine
> > 2.3) and made the save on session unbind look like
On 12.01.12 16:11, Sheldon Ross wrote:
> In order to get around this, we actually update TurbineSecurity (Turbine 2.3)
> and made the save on session unbind look like this.
IMO it's probably easier to modify the
SecurityService.saveOnSessionUnbind() method as this is meant to be
pluggable in Turb
On 12.01.12 18:47, Thomas Vandahl wrote:
> 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 Turbi
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 t
fresh copy of user data is pulled in before saving, so it
> doesn't overwrite a password/email update on logout.
>
>
> > From: wef...@gmail.com
> > Date: Thu, 12 Jan 2012 03:42:43 +0800
> > Subject: Re: TorqueUser synchronization problem
> > To: user@turbi
tLastLogin());
if(fresh != null) getService().saveOnSessionUnbind(fresh);
}
Makes sure a fresh copy of user data is pulled in before saving, so it doesn't
overwrite a password/email update on logout.
> From: wef...@gmail.com
> Date: Thu, 12 Jan 2012 03:42:43 +0800
>
Hello,
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?
Regards
Weffen
在 2012-1-12，3:37，Thomas Vandahl 写道：
> On 11.01.12 20:04
On 11.01.12 20:04, Weffen Cheung wrote:
> Sometimes I update a user record not only after the user login. For example,
> I want to update userB's record when userA login. For this case, we cannot
> use data.getUser().save(), is it right?
Well, there is TurbineSecurity.getUser(userName) which giv
Hello Thomas,
Thanks for your reply.
Sometimes I update a user record not only after the user login. For example, I
want to update userB's record when userA login. For this case, we cannot use
data.getUser().save(), is it right?
Thanks!
Weffen
在 2012-1-12，上午2:58， Thomas Vandahl 写道：
> Hi,
>
Hi,
On 11.01.12 11:19, Weffen Cheung wrote:
> I have used turbine as my products for a few years, but i am not familiar
> with TorqueUser. When I modify some user data directly with jdbc, I found
> that the data in data.getUser() is still the old data, it cannot synchronize
> automatically.
>
10 matches
Mail list logo
