Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.0.0
    • Component/s: portlet container
    • Labels:
      None

      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?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                adouma Ate Douma
                Reporter:
                cziegeler Carsten Ziegeler
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: