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

        Eric Dalquist created issue -
        David DeWolf made changes -
        Field Original Value New Value
        Fix Version/s 1.1.0 [ 12310687 ]
        Assignee David DeWolf [ ddewolf ]
        Hide
        David DeWolf added a comment -

        Just some brainstorming here. . .

        What about the same feature but implemented a little differently. The idea would be to have the "administrative" invocation match the rest of the portlet invocations and would be similar to the load() invocation currently supported by the container. Public API changes would include:

        Modifications:
        ---------------------
        PortletContainer.admin(ServletRequest, ServletResponse, PortletWindow)

        Additions:
        ---------------------
        AdministrativePortletRequest
        AdministrativePortletResponse
        AdministrativeService
        + process(AdministrativePortletRequest, AdministrativePortletResponse);

        Show
        David DeWolf added a comment - Just some brainstorming here. . . What about the same feature but implemented a little differently. The idea would be to have the "administrative" invocation match the rest of the portlet invocations and would be similar to the load() invocation currently supported by the container. Public API changes would include: Modifications: --------------------- PortletContainer.admin(ServletRequest, ServletResponse, PortletWindow) Additions: --------------------- AdministrativePortletRequest AdministrativePortletResponse AdministrativeService + process(AdministrativePortletRequest, AdministrativePortletResponse);
        Hide
        Eric Dalquist added a comment -

        That would work quite well (and be much simpler +1 there).

        Show
        Eric Dalquist added a comment - That would work quite well (and be much simpler +1 there).
        Hide
        David DeWolf added a comment -

        503473

        Show
        David DeWolf added a comment - 503473
        David DeWolf made changes -
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Resolved [ 5 ]
        David DeWolf made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Mark Thomas made changes -
        Workflow jira [ 12395727 ] Default workflow, editable Closed status [ 12564912 ]
        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12564912 ] jira [ 12586338 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development