« Return to Thread: [jira] Created: (PLUTO-558) Change FilterManagerService to use portlet entity

[jira] Commented: (PLUTO-558) Change FilterManagerService to use portlet entity

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View in Thread


    [ https://issues.apache.org/jira/browse/PLUTO-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705628#action_12705628 ]

Carsten Ziegeler commented on PLUTO-558:
----------------------------------------

I guess it somehow depends what the portal uses as the manageable unit: portlet entity or window. But I agree that we could use the PortletWindow for the signature as well.

For your suggestion to drop PortletEntity:+1

> Change FilterManagerService to use portlet entity
> -------------------------------------------------
>
>                 Key: PLUTO-558
>                 URL: https://issues.apache.org/jira/browse/PLUTO-558
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlet container
>    Affects Versions: 2.0.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: 2.0.0
>
>
> the current FilterManagerService interface uses the
> PortletApplicationDefinition and the portlet name (string):
> getFilterManager(PortletApplicationDefinition portletAppDD, String
> portletName, String lifeCycle)
> I would like to change the signature of this method to use the
> PortletEntity:
> getFilterManager(PortletEntity, String lifeCycle).
> This would allow portals to provide different filter chains based on a
> portlet entity.

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

 « Return to Thread: [jira] Created: (PLUTO-558) Change FilterManagerService to use portlet entity