Jon Stevens wrote:
>
> on 7/5/01 5:32 AM, "Diethelm Guallar, Gonzalo" <[EMAIL PROTECTED]>
> wrote:
>
> > I need to invoke an operation whenever a session times out.
> > Is this the "orthodox" approach in Turbine?
> >
> > * Define MyUser as inheriting from TurbineUser, and implement
> > its valueUnbound():
> >
> > public void valueUnbound(HttpSessionBindingEvent hsbe)
> > {
> > super.valueUbbound(hsbe);
> > call_super_dooper_operation();
> > }
> >
> > * Set TR.props:
> >
> > services.SecurityService.user.class=myPackage.MyUser
> >
> > Does this look right? I kinda expected this would be more "pluggable",
> > and maybe it is, that's why I'm checking to see if I'm totally off
> > track here. Thanks,
>
> That would work and is perfectly "pluggable". The only thing else I would
> suggest is that you just place an object into the Session yourself and use
> the standard ServletAPI to do things (ie: have the object implemnt the
> HttpSessionBinding* interface so that the valueUnBound/Bound methods are
> called on the object).
>
> -jon
>
It seem that depends on the importance of the stuff to make when the
user is unbouded.
I'm experiencing this propositon, and it look that of the TurbineUser
was unboud correctly, the object placed in their session was unbouded
after, at least at the shutdown of the server. That is because the
session is invalidated, so like the Servlet Api says, the object
implementing HttpSessionBinding* are unboudes after, with any priority..
Jerome
--
JK:Y a-t-il un mot fran�ais pour tamagotchi (cette petite b�te
�lectronique) ?
JR:J'ai en pr�paration un cathogauchi pour PC. D�s qu'il sera pr�t je
le poste.
-+- in: Guide du Cabaliste Usenet - L'�cran catholique de la Cabale -+-
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
