[JS2-315] Premature access to portal can break access to portlets.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-M4
• Fix Version/s: 2.0-M4, 2.0-FINAL, 2.1-dev, 2.1
• Component/s: Deployment, Portlet Entities and Preferences
• Assignee: Ate Douma
• Reporter: Scott Weaver
• Created: 22/Jul/05 02:01
• Updated: 04/Oct/11 21:38
• Resolved: 14/Apr/06 04:00

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.