You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by je...@jakarta.apache.org on 2004/08/15 23:58:20 UTC

[jira] Created: (JS2-108) TreeControl taglib caches PortletURLs thereby causing render parameters (of other portlets) to get lost

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS2-108

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS2-108
    Summary: TreeControl taglib caches PortletURLs thereby causing render parameters (of other portlets) to get lost
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Jetspeed 2
 Components: 
             Other
   Versions:
             2.0-dev/cvs

   Assignee: 
   Reporter: Ate Douma

    Created: Sun, 15 Aug 2004 2:58 PM
    Updated: Sun, 15 Aug 2004 2:58 PM
Environment: WindowsXP SP1, Tomcat 4.1.30, J2SE 1.4.2_04

Description:
The Portlet Application Manager uses the TreeControl taglib for navigation of the Application Tree.
On first usage, the TreeControl is filled with Action URLs for each of the tree nodes to render.
Because these are thereafter cached, portlet render parameters (which are stored in the saved Portlet URL) are frozen to this initialization time.
Selecting a TreeControl node on a page which also contains other portlets therefore results in losing any changed render state (parameter s) of those portlets. 
Because by default SesionNavigationalState is used in J2, window and portlet mode do carry over, but if PathNavigationState would be used, those settings also would be lost.

In general: Portlet URLs may *never* be cached. Saving render parameters in the Portlet Session would fix this, but would not be portable according to the JSR-168 specification (another serious limitation of the spec I think).

Solution: don't cache Portlet URLs in the TreeControl taglib component.


---------------------------------------------------------------------
JIRA INFORMATION:
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


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

[jira] Resolved: (JS2-108) TreeControl taglib caches PortletURLs thereby causing render parameters (of other portlets) to get lost

Posted by je...@jakarta.apache.org.
Message:

   The following issue has been resolved as FIXED.

   Resolver: Jeremy Ford
       Date: Thu, 2 Sep 2004 9:14 AM

Tag changed to substitute action urls dynamically during tree render
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS2-108

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS2-108
    Summary: TreeControl taglib caches PortletURLs thereby causing render parameters (of other portlets) to get lost
       Type: Bug

     Status: Resolved
   Priority: Major
 Resolution: FIXED

    Project: Jetspeed 2
 Components: 
             Other
   Fix Fors:
             2.0-dev/cvs
   Versions:
             2.0-dev/cvs

   Assignee: 
   Reporter: Ate Douma

    Created: Sun, 15 Aug 2004 2:58 PM
    Updated: Thu, 2 Sep 2004 9:14 AM
Environment: WindowsXP SP1, Tomcat 4.1.30, J2SE 1.4.2_04

Description:
The Portlet Application Manager uses the TreeControl taglib for navigation of the Application Tree.
On first usage, the TreeControl is filled with Action URLs for each of the tree nodes to render.
Because these are thereafter cached, portlet render parameters (which are stored in the saved Portlet URL) are frozen to this initialization time.
Selecting a TreeControl node on a page which also contains other portlets therefore results in losing any changed render state (parameter s) of those portlets. 
Because by default SesionNavigationalState is used in J2, window and portlet mode do carry over, but if PathNavigationState would be used, those settings also would be lost.

In general: Portlet URLs may *never* be cached. Saving render parameters in the Portlet Session would fix this, but would not be portable according to the JSR-168 specification (another serious limitation of the spec I think).

Solution: don't cache Portlet URLs in the TreeControl taglib component.


---------------------------------------------------------------------
JIRA INFORMATION:
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


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org