> -----Message d'origine----- > De : Weaver, Scott [mailto:Sweaver@;rippe.com] > Envoy� : vendredi 8 novembre 2002 15:25 > � : 'Jetspeed Users List' > Objet : RE: data.getUser() is null, not data.getUserFromSession() ... > > > > And I changed the properties file to point to this logout > class of course. > > Then you have changed the "action.logout" property to > MyLogOut, correct?
correct > Turbine treats the designated action.logout and action.login > differently than other actions. My own experiences with this > issue have shown that this causes nothing but headaches. The > problems you are experiencing could be caused by this. > Another side-effect that caused me lots of problems is that > the session-based pull tools were not immediately refreshed. > This meant that after log out and/or log in the current user > would still have the previous user's set of pull tools for > the duration of that request. However, all subsequent > requests worked correctly. Seems to be the exact same trouble ! > What I did... > In my non-jetspeed turbine apps, I have always used custom > log out and log in classes but did not register it with > action.logout or action.login. > > hth, > Scott Well, I think I'll stay with the getUserFromSession in those classes, but I'll have a closer look to the diff between getUser & getUserFromSession (what's the difference ???? :)) Thanks, Aurelien -- To unsubscribe, e-mail: <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-user-help@;jakarta.apache.org>
