Uploaded image for project: 'Jetspeed 2'
  1. Jetspeed 2
  2. JS2-315

Premature access to portal can break access to portlets.

    Details

      Description

      When the portal is first deployed, and a user attempts to access the portal before the portlet apps have been deployed into Tomcat, the portlets do not display correctly. This is to be expected, as the target portlet app is yet to register itslef into the portlet registry. However, due to caching of portlet windows and hence portlet entities, this cannot be corrected and the portal must be bounced.

      To fix this, I have added logic to the PortletEntityImpl that allows it to try and load it's related PortletDefinition by looking using the Fragment that is associated with saod entity to pull the PortletDefinition from the registry, even in the case of the PortletEntity being cached.

        Attachments

          Activity

            People

            • Assignee:
              adouma Ate Douma
              Reporter:
              weaver Scott T Weaver
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: