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

          Hide
          Ate Douma added a comment -

          In the related JIRA issue for Jetspeed, JS2-1013, I've provided a little bit background why Pluto container no longer needs the PortletEntity:

          With the major rewrite of the Pluto 2.0.0 container, the need and usage of the PortletEntity no longer is needed within Pluto itself, nor in Jetspeed.

          The Portlet specification (2.0) describes the concept of a PortletEntity as follows in PLT.5.3.1:

          "At runtime, when serving requests, one or more preference objects are associated with a portlet.
          The resulting association of a specific preference object with a portlet is called the portlet entity.
          This concept is abstract. There is not a concrete object that represents the portlet entity.
          The portal / portlet container merely associates the proper preference object with the context that is passed to the executing portlet."

          As the Pluto container does not impose in any way how the proper preference object is associated, but delegates this to the portal (like Jetspeed) for which it provides the current PortletWindow as selector,
          it is completely up to the embedding portal how to select the proper preference object. Within the Pluto container, there is no concrete usage anymore of a PortletEntity nor wat it should be or do, if it even exists.

          Show
          Ate Douma added a comment - In the related JIRA issue for Jetspeed, JS2-1013 , I've provided a little bit background why Pluto container no longer needs the PortletEntity: With the major rewrite of the Pluto 2.0.0 container, the need and usage of the PortletEntity no longer is needed within Pluto itself, nor in Jetspeed. The Portlet specification (2.0) describes the concept of a PortletEntity as follows in PLT.5.3.1: "At runtime, when serving requests, one or more preference objects are associated with a portlet. The resulting association of a specific preference object with a portlet is called the portlet entity. This concept is abstract. There is not a concrete object that represents the portlet entity. The portal / portlet container merely associates the proper preference object with the context that is passed to the executing portlet." As the Pluto container does not impose in any way how the proper preference object is associated, but delegates this to the portal (like Jetspeed) for which it provides the current PortletWindow as selector, it is completely up to the embedding portal how to select the proper preference object. Within the Pluto container, there is no concrete usage anymore of a PortletEntity nor wat it should be or do, if it even exists.
          Hide
          Ate Douma added a comment -

          Done

          Show
          Ate Douma added a comment - Done

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development