Uploaded image for project: 'Pluto'
  1. Pluto
  2. PLUTO-371 Portlet Filter
  3. PLUTO-441

Redeploy of a portlet doesn't effect filter implementation

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Minor
    • Resolution: Incomplete
    • 1.1-286-COMPATIBILITY
    • 1.1-286-COMPATIBILITY
    • portal driver
    • None

    Description

      Portlet Filter are registered at the SupportedModesServiceImpl.loadPortletModes() which runs only once. Therefore changes at the portletDD are not recognized.

      Maybe we could use a similiar method as we did with the eventprovider? Make the FilterManager request dependant and look for the filter at every request. Then there is no need for a global (static) map of filters.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            chrisra Christian Raschka
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment