Pluto
  1. Pluto
  2. PLUTO-301

Administrative lifcycle hooks in portlet servlet

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.0-beta2
    • Fix Version/s: 1.1.0
    • Component/s: portlet container
    • Labels:
      None

      Description

      An extension point is needed to run portal provided code within the portlet's servlet-context.

      The concept is another pluto specific servlet in the web.xml that listens to a URL like: /pluto/admin/*

      The string after hard path would correspond to a key in a adminServices Map injected into the portlet container.

      The values of the Map would be some sort of PortletAdminService interface implementations provided by the portal.

      The portlet container would provide an API so the portal could call container.runAdminService("foo", request, response) and the PortalAdminService interface impl keyed by the string "foo" would be executed via a cross context dispatch.

      The PortletAdminService would have a method that had access to an AdministrativePortletRequest and AdministrativePortletResponse.

        Activity

          People

          • Assignee:
            David DeWolf
            Reporter:
            Eric Dalquist
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development