[PLUTO-559] Drop PortletEntity interface

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: portlet container
• Assignee: Ate Douma
• Reporter: Carsten Ziegeler
• Created: 05/May/09 06:03
• Updated: 14/May/09 12:48
• Resolved: 14/May/09 12:48

Description

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?

Issue Links

• is related to: JS2-1013 Remove obsolete usage of and dependency on Pluto provided PortletEntity interface as it is no longer used within Jetspeed either