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/03/02 03:08:51 UTC

[jira] Resolved: (PLUTO-321) Give DefaultPortletInvokerService.invoke() protected access

     [ https://issues.apache.org/jira/browse/PLUTO-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David DeWolf resolved PLUTO-321.
--------------------------------

    Resolution: Fixed

I opened it up but marked it as final.  I'm not sure why I'm hesitant to provide access to it.  I guess I am since it's one of those internal methods that could significantly impact how pluto behaves and could also change in the future. . ..let me know if you need to extend it.

> Give DefaultPortletInvokerService.invoke() protected access
> -----------------------------------------------------------
>
>                 Key: PLUTO-321
>                 URL: https://issues.apache.org/jira/browse/PLUTO-321
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlet container
>    Affects Versions: 1.1.0
>            Reporter: David Hay
>         Assigned To: David DeWolf
>            Priority: Minor
>             Fix For: 1.1.1
>
>
> Related to PLUTO-269, I'd like to see the invoke() method in DefaultPortletInvokerService given protected access.  I've added a custom phase to the portlet spec for our application and would like to use the existing invoke method to call into the portlet application with a new methodID and request/response subclasses.

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