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

["Wayne Holder (JIRA)" <pl...@jakarta.apache.org>]

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

To correct my last comment, I forgot to also set crossContext="true" in the <context> tab.  After doing this, I was able to verify that application level session information set in a portlet can be accessed by a servlet running in the same web applciation if the following things are all true:

1. The <context> tag sets crossContext="true"
2. The <connector> tag sets emptySessionPath="true"
3. You are using Tomcat 5.5.4, or later

Of course, one thing that seems crazy to me is that I have to do these things when the portlet calling the servlet resides in the very same web app and, therefore, shares the same context path.

IMO, JSR-168 does not make it at all clear what the proper context path for a portlet should be.  That is, should the portlet take the context of the portal app where it's displayed, or the web app where the portlet's class is defined?  I think these things need to be specified in much more detail.

> 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