You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "David DeWolf (JIRA)" <ji...@apache.org> on 2007/02/04 05:33:05 UTC

[jira] Commented: (PLUTO-301) Administrative lifcycle hooks in portlet servlet

    [ https://issues.apache.org/jira/browse/PLUTO-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470022 ] 

David DeWolf commented on PLUTO-301:
------------------------------------

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);


> Administrative lifcycle hooks in portlet servlet
> ------------------------------------------------
>
>                 Key: PLUTO-301
>                 URL: https://issues.apache.org/jira/browse/PLUTO-301
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlet container
>    Affects Versions: 1.1.0-beta2
>            Reporter: Eric Dalquist
>         Assigned To: David DeWolf
>             Fix For: 1.1.0
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.