I've seen many posts related to this, but no solutions that work for me. My understanding is that the HttpSession backing of PortletSession is the portal application context session, not the HttpSession for the portlet context. Therefore, when the portlet applications servlet tries to get the session value, it can't.
I've seen posts (http://issues.apache.org/jira/browse/PLUTO-53) that say it is a pluto/Tomcat issue, and say setting crossContext="true" and emptySessionPath="true" will solve the problem. This didn't work for me either. I'm running Jetspeed 2.0 FINAL on Tomcat 5.5.12. Anyone solve this problem? > hello > > Andrew Hill a écrit : > > > Firstly you need to explicitly state that its Session Application Scope: > > > > PortletSession.setAttribute("listImage", m, > > PortletSession.APPLICATION_SCOPE); > > i've just tried this, and it didn't work... > > > > > Secondly check that your actually getting the same session in your > > servlet. If you dont see anything in the attributes it would indicate > > that its probably a different session, as even the PORTLET_SCOPE > > attributes would show up with some namespacing applied. > > i don't really understand what you mean... > > > > > How are you 'calling' the servlet? Is it in the same webapp? > > actually, my servlet is in the same webapp, and is generating a png > image, so it's called by an <img> markup written in my portlet... > > > Luc > > -- > Luc FOUIN - Stagiaire Aptiwan > 14 rue Niepce > 75014 Paris > Tél : 06 77 95 17 24 > Mél : [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
