Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major 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?

        Issue Links

          Activity

          Carsten Ziegeler created issue -
          Ate Douma made changes -
          Field Original Value New Value
          Assignee Ate Douma [ adouma ]
          Ate Douma made changes -
          Link This issue is related to JS2-1013 [ JS2-1013 ]
          Ate Douma made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Mark Thomas made changes -
          Workflow jira [ 12462573 ] Default workflow, editable Closed status [ 12565118 ]
          Mark Thomas made changes -
          Workflow Default workflow, editable Closed status [ 12565118 ] jira [ 12585882 ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development