[ http://issues.apache.org/jira/browse/JS2-315?page=all ]
Ate Douma resolved JS2-315:
---------------------------
Fix Version: 2.1
2.1-dev
Resolution: Fixed
Applied an improved fix.
Now when a Portlet (Application) isn't available when rendering a fragment, as
for example by default for the ThirdParty portlets,
you'll get an error message like:
" Failed to retrieve Portlet Definition for GooglePortlet::GooglePortlet"
This doesn't solve issues like JS2-234, but at least the error message now is
more to the point.
> 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: Ate Douma
> Fix For: 2.0-M4, 2.0-FINAL, 2.1, 2.1-dev
>
> 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]
