You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-user@portals.apache.org by Eugeny N Dzhurinsky <eu...@jdevelop.com> on 2005/07/08 18:31:02 UTC

Popup-windows

Hi!
I need some advice - our portal have the "edit" page, which needs to be edited
using the popup-windows. We are populating the windows, which are regular JSP
pages placed on some context where portlet is deployed in the container. The
JSP should read the data provided by the user, and store the objects in the
session. The portlet should use the same session to get the objects produced
by the JSP page. But it seems the sessions are DIFFERENT for the JSP pages and
portlet - i.e. the JSP page can read and write the object for the key "test"
with session.getAttribute("test")/session.setAttribute("test"), but portlet
can't get access to the object for the key "test" using
RenderRequest.getPortletSession().getAttribute("test").

What's wrong here, and how to pass the object to the portlet session from 
"outside" the portlet (as far as I understood the concepts, the 
HttpSession != PortletSession).

Re: Popup-windows

Posted by Eugeny N Dzhurinsky <eu...@jdevelop.com>.
On Fri, Jul 08, 2005 at 07:31:02PM +0300, Eugeny N Dzhurinsky wrote:
> Hi!
> I need some advice - our portal have the "edit" page, which needs to be edited
> using the popup-windows. We are populating the windows, which are regular JSP
> pages placed on some context where portlet is deployed in the container. The
> JSP should read the data provided by the user, and store the objects in the
> session. The portlet should use the same session to get the objects produced
> by the JSP page. But it seems the sessions are DIFFERENT for the JSP pages and
> portlet - i.e. the JSP page can read and write the object for the key "test"
> with session.getAttribute("test")/session.setAttribute("test"), but portlet
> can't get access to the object for the key "test" using
> RenderRequest.getPortletSession().getAttribute("test").
> 
> What's wrong here, and how to pass the object to the portlet session from 
> "outside" the portlet (as far as I understood the concepts, the 
> HttpSession != PortletSession).

Well,  as I found, it is not possible to share the portlet session with JSP
page :((
For now we solved this problem using the "crunch" - the shared session object
is stored in the file (serialized HashMap). At least this works.