[ http://issues.apache.org/jira/browse/JS2-315?page=comments#action_12316393 ]
David Sean Taylor commented on JS2-315: --------------------------------------- thats fine then im actually experiencing the same problem here (when I forget to deploy my app, then hit the page) so Im +1 on this one just wanted to make sure it wasnt the portlet window accessor situation thanks > Premature access to portal can break access to portlets. > -------------------------------------------------------- > > Key: JS2-315 > URL: http://issues.apache.org/jira/browse/JS2-315 > Project: Jetspeed 2 > Type: Bug > Components: Deployment, Portlet Entities and Preferences > Versions: 2.0-M4 > Reporter: Scott T Weaver > Assignee: Scott T Weaver > Fix For: 2.0-M4, 2.0-FINAL > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
