portals-pluto-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pluto-...@jakarta.apache.org
Subject [jira] Commented: (PLUTO-53) Pluto violates PLT.15.4
Date Thu, 14 Oct 2004 13:15:56 GMT
The following comment has been added to this issue:

     Author: David DeWolf
    Created: Thu, 14 Oct 2004 6:15 AM
A patch has been applied to tomcat (Oct 13, 2004) which allows a work around for this issue.
 I think this bug can now be marked as resolved.   If someone else can confirm that the patch
works for them, please mark the bug as resolved.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: PLUTO-53
    Summary: Pluto violates PLT.15.4
       Type: Bug

     Status: Reopened
   Priority: Major

    Project: Pluto
             portlet container
             Current CVS

   Assignee: David DeWolf
   Reporter: Ken Weiner

    Created: Wed, 30 Jun 2004 3:47 PM
    Updated: Thu, 14 Oct 2004 6:15 AM
Environment: Pluto Portal Driver + the Pluto Container or uPortal + the Pluto Container

The JSR 168 Portlet Specification (PLT.15.4) states that Portlets are supposed to be able
to communicate information with other Servlets and JSPs that are part of the same Portlet
Application via their session.  It appears that this ability is not possible with Portlet
Applications running in Pluto.

If you examine the session ID of the session within a Portlet and then examine the session
ID within a Servlet that was accessed directly by the user with a URL pointing to that Servlet,
you will see that the session IDs do not match, and apparently they should.

For a demonstration of this, please deploy and examine the following Portlet: http://www.unicon.net/download/PortletSessionTest.war

By the way, the motivation for wanting to share information via the session in this way comes
from a need to handle file downloads from a Portlet.

For reference, see the recent discussion thread on the Pluto User Mailing List:


This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message