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 "Ate Douma (JIRA)" <ji...@apache.org> on 2009/05/14 14:05:45 UTC

[jira] Assigned: (PLUTO-559) Drop PortletEntity interface

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

Ate Douma reassigned PLUTO-559:
-------------------------------

    Assignee: Ate Douma

> Drop PortletEntity interface
> ----------------------------
>
>                 Key: PLUTO-559
>                 URL: https://issues.apache.org/jira/browse/PLUTO-559
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlet container
>    Affects Versions: 2.0.0
>            Reporter: Carsten Ziegeler
>            Assignee: Ate Douma
>             Fix For: 2.0.0
>
>
> As discussed in another bug, Ate suggested to drop the PortletEntity interface:
> Furthermore, I'm actually tempted to propose we drop PortletEntity as a qualified interface all together as Pluto (nor Jetspeed) doesn't use PortletEntity at all.
> For Jetspeed, I've already enhanced our (extended) PortletWindow to provide access to the PortletEntity (PreferencesSet) *ID* with method String getPortletEntityId() and also added getPortletDefinition() directly to PortletWindow.
> That greatly cleans up the code base as the PortletEntity 'intermediate' (now reduced to just an empty interface) then can be cut out from all the PortletWindow->PortletDefinition access usages.
> WDYT?

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