Jetspeed 2
  1. Jetspeed 2
  2. JS2-198

Portlets don't use user-specific preferences. The Portlet Preferences for anon user are always used.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: 2.1-dev, 2.1
    • Labels:
      None
    • Environment:
      jdk 1.4.2_03, win2000, tomcat-5.0.30

      Description

      Portlets don't use user-specific preferences. For example, the Bookmarks Portlet on default.psml always use preferences for anon user. The Portlet reads and writes PortletPreferences from/to the table PREFS_NODE with FULL_PATH=/portlet_entity/db-18/no-principal for authenticated and not authenticated users.

      It seems that PortletRendererImpl and JetspeedPowerTool don't pass the user principal to the PortletWindowAccessor. PortletWindowAccessor.validateWindow has to pass the principal to PortletEntityAccessComponent too.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Closed Closed
        675d 13h 47m 1 Ate Douma 27/Nov/06 10:52
        Ate Douma made changes -
        Fix Version/s 2.1-dev [ 12310686 ]
        Resolution Duplicate [ 3 ]
        Status Open [ 1 ] Closed [ 6 ]
        Hide
        Ate Douma added a comment -

        This issue is stale, but JS2-449 is (AFAIK) similar and actively worked on, so closing this one.

        Show
        Ate Douma added a comment - This issue is stale, but JS2-449 is (AFAIK) similar and actively worked on, so closing this one.
        Michael Lipp made changes -
        Fix Version/s 2.0-POST [ 12310617 ]
        Description Portlets don't use user-specific preferences. For example, the Bookmarks Portlet on default.psml always use preferences for anon user. The Portlet reads and writes PortletPreferences from/to the table PREFS_NODE with FULL_PATH=/portlet_entity/db-18/no-principal for authenticated and not authenticated users.

        It seems that PortletRendererImpl and JetspeedPowerTool don't pass the user principal to the PortletWindowAccessor. PortletWindowAccessor.validateWindow has to pass the principal to PortletEntityAccessComponent too.
        Portlets don't use user-specific preferences. For example, the Bookmarks Portlet on default.psml always use preferences for anon user. The Portlet reads and writes PortletPreferences from/to the table PREFS_NODE with FULL_PATH=/portlet_entity/db-18/no-principal for authenticated and not authenticated users.

        It seems that PortletRendererImpl and JetspeedPowerTool don't pass the user principal to the PortletWindowAccessor. PortletWindowAccessor.validateWindow has to pass the principal to PortletEntityAccessComponent too.
        David Sean Taylor made changes -
        Field Original Value New Value
        Type Bug [ 1 ] Improvement [ 4 ]
        Hide
        David Sean Taylor added a comment -

        With the current implemention, in order to get user-specific preferences, you need to put the page under the user's directory. I believe this is sometimes the desired behavior, as it clearly defines how preferences are shared over the folder, page hieararchy. Prefs are identified by the instance on a given page. This leads to prefs being shared in common pages. I can also see where we would want prefs to be shared in a common page on a per user basis. But I don't really see this as a bug, but more of an enhancement since the spec does not address the concept of pages in jetspeed.

        Show
        David Sean Taylor added a comment - With the current implemention, in order to get user-specific preferences, you need to put the page under the user's directory. I believe this is sometimes the desired behavior, as it clearly defines how preferences are shared over the folder, page hieararchy. Prefs are identified by the instance on a given page. This leads to prefs being shared in common pages. I can also see where we would want prefs to be shared in a common page on a per user basis. But I don't really see this as a bug, but more of an enhancement since the spec does not address the concept of pages in jetspeed.
        Artem Grinshtein created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Artem Grinshtein
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development