PortletSession attributes

[Zilber Laurent <lz...@axway.com>]

Hello,
I believe it's more of a pluto problem, but I was wondering if anyone
else noticed this:

I have a portlet that store an attribute in APPLICATION_SCOPE and
display it on the page.
Let's say the default value (user not logged in) is "abc", and the value
for user "test" is "xyz".

If I goto the portlet without login in, the portlet shows "abc"
If I log in as test and go back to the portlet, it still shows "abc" !

If I restart the server, log in as test and go to the portlet, it shows
"xyc",
But login out and trying again gives the same problem...

I traced it and it's not related to browser cache. Basically pluto
RenderRequestImpl.getPortletSession gives me an existing session !
The problem seems related to session handling in Tomcat : when
restarting the server, it serializes sessions on shutdown and
deserializes the session later, hence pluto getting an old
PortletSession with wrong attributes ?!?

I cleared Tomcat's work directory,  added a <Manager pathname="" /> to
the Jetspeed <Context> definition...no changes.

I'm putting a few screenshots.
Any ideas ?

 <<login_2.JPG>>  <<login_1.JPG>> 
__________________________________________
Laurent Zilber  - Synchrony Vantage R&D - AXWAY 

RE: PortletSession attributes

[Zilber Laurent <lz...@axway.com>]

Hello,
Found the problem.
 
Jetspeed 2 invalidates the session when login out.
However if 
- user accesses the portal as 'guest' (i.e whitout login in)
- user displays a portlet that initialize the session (like calling request.getPortletSession())
- user _then_ logs in => user keeps session previously initialized.
 
Jetspeed 2 doesn not invalidate the 'guest' PortletSession when the user logs in.
This is actually coherent with the JSR (as it doesn't really tell when a portal should invalidate Portlet sessions).
 
One could reasonably argue that this should be handled by the portlet if this portlet wants specific behavior for identified/non-identified users.
 
Thus I won't log this in JIRA.
 
And I'll probably stop posting to the list and replying to myself. :)


________________________________

De : Zilber Laurent 
Envoyé : vendredi 22 septembre 2006 17:48
À : jetspeed-user@portals.apache.org
Objet : PortletSession attributes



Hello, 
I believe it's more of a pluto problem, but I was wondering if anyone else noticed this: 

I have a portlet that store an attribute in APPLICATION_SCOPE and display it on the page. 
Let's say the default value (user not logged in) is "abc", and the value for user "test" is "xyz". 

If I goto the portlet without login in, the portlet shows "abc" 
If I log in as test and go back to the portlet, it still shows "abc" ! 

If I restart the server, log in as test and go to the portlet, it shows "xyc", 
But login out and trying again gives the same problem... 

I traced it and it's not related to browser cache. Basically pluto RenderRequestImpl.getPortletSession gives me an existing session !

The problem seems related to session handling in Tomcat : when restarting the server, it serializes sessions on shutdown and deserializes the session later, hence pluto getting an old PortletSession with wrong attributes ?!?

I cleared Tomcat's work directory,  added a <Manager pathname="" /> to the Jetspeed <Context> definition...no changes. 

I'm putting a few screenshots. 
Any ideas ? 

<<login_2.JPG>> <<login_1.JPG>> 
__________________________________________ 
Laurent Zilber  - Synchrony Vantage R&D - AXWAY