You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Wayne Holder (JIRA)" <pl...@jakarta.apache.org> on 2005/01/31 23:09:17 UTC

[jira] Commented: (PLUTO-53) Pluto violates PLT.15.4

     [ http://issues.apache.org/jira/browse/PLUTO-53?page=comments#action_58335 ]
     
Wayne Holder commented on PLUTO-53:
-----------------------------------

I see this issue has been closed because, in theory, this problem is not supposed to happen with Tomcat 5.5.  However, I still see this problem using the RC2 binary release, which comes with Tomcat 5.5 as the servlet container.  In fact, the test servlet ExternalAppScopedAttributeTestCompanionServlet, included with the testsuite app demonstrates this problem with RC2.  Is this issue really fixed in Tomcat 5.5, or only in a later release of 5.5?

> Pluto violates PLT.15.4
> -----------------------
>
>          Key: PLUTO-53
>          URL: http://issues.apache.org/jira/browse/PLUTO-53
>      Project: Pluto
>         Type: Bug
>   Components: portlet container
>     Versions: Current CVS
>  Environment: Pluto Portal Driver + the Pluto Container or uPortal + the Pluto Container
>     Reporter: Ken Weiner
>      Fix For: 1.0.1-rc2

>
> 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:
> http://nagoya.apache.org/eyebrowse/BrowseList?listName=pluto-user@portals.apache.org&by=thread&from=812493
>     

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira